whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix coredns chart value (#8970)

Browse Source 
* fix helm values for coredns

* fix note style
This commit is contained in:
makocchi
2018-06-16 05:16:29 +09:00
committed by k8s-ci-robot
parent f630a57c1c
commit 255ff2014b
2 changed files with 8 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/federation/Values.yaml
+2 -2
View File
@@ -1,10 +1,10 @@
isClusterService: false isClusterService: false
serviceType: "LoadBalancer" serviceType: "LoadBalancer"
middleware: plugins:
kubernetes: kubernetes:
enabled: false enabled: false
etcd: etcd:
enabled: true enabled: true
zones: zones:
- "example.com." - "example.com."
endpoint: "http://etcd-cluster.my-namespace:2379" endpoint: "http://etcd-cluster.my-namespace:2379"
content/en/docs/tasks/federation/set-up-coredns-provider-federation.md
+6 -7
View File
@@ -70,14 +70,14 @@ that CoreDNS is deployed as a Kubernetes application service.
- `serviceType` specifies the type of Kubernetes service to be created - `serviceType` specifies the type of Kubernetes service to be created
for CoreDNS. You need to choose either "LoadBalancer" or "NodePort" to for CoreDNS. You need to choose either "LoadBalancer" or "NodePort" to
make the CoreDNS service accessible outside the Kubernetes cluster. make the CoreDNS service accessible outside the Kubernetes cluster.
- Disable `middleware.kubernetes`, which is enabled by default by - Disable `plugins.kubernetes`, which is enabled by default by
setting `middleware.kubernetes.enabled` to false. setting `plugins.kubernetes.enabled` to false.
- Enable `middleware.etcd` by setting `middleware.etcd.enabled` to - Enable `plugins.etcd` by setting `plugins.etcd.enabled` to
true. true.
- Configure the DNS zone (federation domain) for which CoreDNS is - Configure the DNS zone (federation domain) for which CoreDNS is
authoritative by setting `middleware.etcd.zones` as shown above. authoritative by setting `plugins.etcd.zones` as shown above.
- Configure the etcd endpoint which was deployed earlier by setting - Configure the etcd endpoint which was deployed earlier by setting
`middleware.etcd.endpoint` `plugins.etcd.endpoint`
Now deploy CoreDNS by running Now deploy CoreDNS by running
@@ -105,8 +105,7 @@ coredns-provider.conf has below format:
- `zones` is the federation domain for which CoreDNS is authoritative and is same as --dns-zone-name flag of `kubefed init`. - `zones` is the federation domain for which CoreDNS is authoritative and is same as --dns-zone-name flag of `kubefed init`.
- `coredns-endpoints` is the endpoint to access CoreDNS server. This is an optional parameter introduced from v1.7 onwards. - `coredns-endpoints` is the endpoint to access CoreDNS server. This is an optional parameter introduced from v1.7 onwards.
*Note: middleware.etcd.zones in CoreDNS configuration and --dns-zone-name {{< note >}}**Note**: *plugins.etcd.zones in CoreDNS configuration and --dns-zone-name flag to kubefed init should match.*{{< /note >}}
flag to kubefed init should match.*
## Setup CoreDNS server in nameserver resolv.conf chain ## Setup CoreDNS server in nameserver resolv.conf chain