Commit 569a8ed4 authored by Marco Lorini's avatar Marco Lorini
Browse files

2020-10-15 ML: fix readme

parent 2f359e14
......@@ -14,10 +14,10 @@ If you want create the Kubernetes clusters on Openstack and you use Juju tool to
## Environment configuration
Before starting it is necessary create several Kubernetes clusters to make the federation. One cluster will be the Host (Host Cluster), in which will be install the KubeFed (Control Plane), and the remaining clusters will be the Members (Member Cluster).
To create the clusters on Openstack, it is possible to use the follow Juju bundle in the Documention section.
To create the clusters on Openstack, it is possible to use the Juju bundle in the Documention section.
Once all the clusters for federation have been created, it is useful to collect all cluster access configurations (.kube/config) in a single config file. In this way you can easily switch from one cluster to another.
Below is an example:
Below an example:
```bash
apiVersion: v1
......@@ -344,8 +344,8 @@ spec:
$ kubectl --context=<host-cluster-context> create -f resource/externaldns.yaml
```
The previous configuration is specific to integrate ExternalDNS with the Ingress DNS Multi-Cluster, in this way it will be possible to obtain the information it needs through the "DNSEndpoint" object. The DNSEndpoint object will be created when the Multi-Cluster is configured (see below).
pdns-api-key
The previous configuration is specific to integrate ExternalDNS with the Multi-Cluster Ingress DNS , in this way it will be possible to obtain the ingress information through the "DNSEndpoint" object. The DNSEndpoint object will be created when the Multi-Cluster Ingress DNS is configured (see below).
The main configuration are:
- **source**: the field represents the type of resources for which it is necessary create a DNS record. For example: service or ingress. In this case the source value is `crd` for Multi-Cluster Ingress DNS integration;
......@@ -484,7 +484,7 @@ spec:
$ kubectl --context=<host-cluster-context> create -f resource/federated_ingress.yaml
```
In the "host" field the "<domain>" string must be the same that you insert in the "domain-filter" field for ExternalDNS configuration.
In the "host" field the "domain" string must be the same that you insert in the "domain-filter" field for ExternalDNS configuration.
### List federated resources
......@@ -519,4 +519,6 @@ spec:
$ kubectl --context=<host-cluster-context> create -f resource/ingressdnsrecord.yaml
```
The name of IngressDNSRecord must be the same of the ingress resource and the value in "hosts" field must matches the "host" field in the ingress configuration.
\ No newline at end of file
The name of IngressDNSRecord must be the same of the ingress resource and the value in "hosts" field must matches the "host" field in the ingress configuration.
Now the Multi-Cluster Ingress DNS mechanism can start to retrive the ingress endpoints and the ExternalDNS can configure your DNS Provider.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment