dns-custom-namerserver: break down the page into mutliple sections #8900

neolit123 · 2018-06-04T19:29:11Z

This page is currently about kube-dns and is a bit outdated.
Introduce the heading # Customizing kube-dns.

Introduce a separate section about CoreDNS.

/assign @Bradamant3
/assign @rajansandeep
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews

Updates:
kubernetes/kubeadm#843

k8sio-netlify-preview-bot · 2018-06-04T19:29:14Z

Deploy preview for kubernetes-io-vnext-staging processing.

Built with commit 39c799f

https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5b1fc58d8df8941eb6cf08d4

This page is currently about kube-dns and is a bit outdated. Introduce the heading `# Customizing kube-dns`. Introduce a separate section about CoreDNS.

neolit123 · 2018-06-04T19:30:29Z

@Bradamant3 a new section about CoreDNS was added thanks to @rajansandeep .

rajansandeep · 2018-06-04T19:42:28Z

@johnbelamaric @chrisohaver PTAL to see if something needs to be added/modified.

fturib · 2018-06-07T15:49:07Z

/cc @chrisohaver - can you review asap ? Thanks !

chrisohaver · 2018-06-07T16:05:38Z

I see nothing technically incorrect here. Although, organizationally, this information is presented as "How to configure CoreDNS" ... and it only covers the kube-dns equivalent functionality (stubdomains, nameservers, federation). More precisely, it shows examples of those options in kube-dns, and how they can be defined in CoreDNS.

A true "How to configure CoreDNS" would be much more extensive, also covering various use cases that kube-dns cannot handle. So I'd suggest we re-introduce this CoreDNS section as a "Moving from kube-dns to CoreDNS" configuration migration section.

Bradamant3 · 2018-06-07T16:45:49Z

@neolit123 I still need to do some fairly heavy copyediting and fixing of headings in a review -- I'll get to it this afternoon, but you might want to hold off on responding to other comments until I get my review in. Apologies for delay.

fturib

some proposition of improvement...

fturib · 2018-06-07T18:54:14Z

content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md

 {{% /capture %}}

+# Customizing CoreDNS
+
+This section provides with details on [CoreDNS](https://coredns.io/) as a service discovery.



it is possible to add here a link to the page Using CoreDNS for Service Discovery ?

fturib · 2018-06-07T18:55:16Z

content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md

+CoreDNS is available as an option in Kubernetes starting from v1.9.
+It is currently a [GA feature](https://github.com/kubernetes/community/blob/master/keps/sig-network/0010-20180314-coredns-GA-proposal.md) and is on course to be [the default](https://github.com/kubernetes/community/blob/master/keps/sig-network/0012-20180518-coredns-default-proposal.md), replacing kube-dns.
+
+


maybe the link to the page "CoreDNS for Service Discovery" should be here ...

fturib · 2018-06-07T18:57:58Z

content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md

+Currently, a number of tools supports the installation of CoreDNS instead of kube-dns.
+If a user wants to migrate from kube-dns to CoreDNS, [a detailed blog](https://coredns.io/2018/05/21/migration-from-kube-dns-to-coredns/) is available to help users in adapting CoreDNS in place of kube-dns.
+
+## What's next


I guess only one # here. (What is next is on same level as kube-dns and CoreDNS

fturib · 2018-06-07T18:59:04Z

content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md

 {{% /capture %}}

+# Customizing CoreDNS
+
+This section provides with details on [CoreDNS](https://coredns.io/) as a service discovery.


"provides details ..." (remove with)

neolit123 · 2018-06-07T21:37:29Z

@Bradamant3 i will combine the future review fixes with the feedback from @fturib about the links.
thanks.

Hey Lubomir, I coypedited pretty heavily because this workflow is so much easier for docs and because I'm trying to help improve everything touching kubeadm as much as possible. But there's one outstanding issue wrt headings and intro content: you can't add a heading 1 to a topic to do what you wanted to do. The page title in the front matter is rendered as a heading 1 and everything else has to start at heading 2. (We still need to doc this better in the docs contributing content, I know.) Instead, I think we need to rewrite the top-of-page intro content to explain better the relationship between kube-dns and CoreDNS. I'm happy to write something, but I thought I'd push this commit first so you can see what I'm doing. Hope it's all clear -- ping here or on Slack with any questions ~ Jennifer

Bradamant3 · 2018-06-08T14:50:19Z

@neolit123 see my commit message. Maybe we have a short-term solution with the comment from chrisohaver ^^ -- just saw it. lmk what you think.

johnbelamaric · 2018-06-08T15:29:02Z

If you like I can take a crack at this one. It really needs a lot of changes to differentiate between the two options and re-organize into the bits that are the same for both and those that are different.

neolit123 · 2018-06-08T15:32:49Z

@Bradamant3 i think this is fine, as is.

@johnbelamaric much appreciated.
you can just push commits on top of this one.

all, i think we should make a 30 minute Zoom meeting outside of regular SIG meetings, possibly after the 1.11 docs freeze, invite SIG-cluster-lifecycle, SIG-docs and SIG-networking representatives and discuss all the DNS related topics - possibly reduce the amount of sparse information.

my 2c.

Bradamant3 · 2018-06-08T16:41:00Z

@johnbelamaric wdyt of holding off on reorg until after 1.11 release? I spent a lot of time copyediting the current structure bc I didn't have bandwidth to think through the kind of work you propose, and I don't have time to provide that kind of feedback again in the 1.11 timeline. But the work you propose is exactly what this page needs, I agree.

Bradamant3 · 2018-06-08T16:47:35Z

Also agree with @neolit123 's idea to meet separately about DNS related topics. It's great to have y'all so involved in helping clean up docs properly, but we need to coordinate timing of efforts better. At the end of the release cycle works for dev, but not for docs. So reorg work, for example, is probably best planned iteratively against master, so that we can merge and publish those commits throughout the release cycle.

johnbelamaric · 2018-06-08T17:01:06Z

Sure, it can wait - I have enough to do :)

Bradamant3 · 2018-06-12T11:47:00Z

@neolit123 I made a few more changes to explain CoreDNS better at the top of the file. Also changed the prerequisite item about required version/s. PTAL, not sure I'm right about versions but we should put something. Thanks!

neolit123 · 2018-06-12T12:30:24Z

content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md

@@ -8,13 +8,16 @@ content_template: templates/task

 {{% capture overview %}}
 This page explains how to configure your DNS Pod and customize the
-DNS resolution process.
+DNS resolution process. In Kubernetes version 1.11 and later, CoreDNS is installed
+by default. See [Configuring CoreDNS](#config-coredns) and 


instead of:
In Kubernetes version 1.11 and later, CoreDNS is installed by default.

we need to say something in the lines of:
In Kubernetes version 1.11, CoreDNS has reached the General Availability status and is installed by default from kubeadm.

so it is GA since 1.11, but only installed by default from kubeadm.

neolit123 · 2018-06-12T12:41:26Z

content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md

-* The cluster must be configured to use the `kube-dns` addon.
+* Kubernetes version 1.6 or later. To work with CoreDNS, version 1.9 or later.
+* The cluster must be configured to use the `kube-dns` add-on. Note that the add-on name
+is the same whether you run kube-dns or CoreDNS.


instead of:

The cluster must be configured to use the kube-dns add-on. Note that the add-on name is the same whether you run kube-dns or CoreDNS.

i suggest we use:

To install CoreDNS as an addon with kubeadm, have a look at kubeadm alpha phase addon.

Bradamant3 · 2018-06-12T13:09:08Z

@neolit123 OK, I think we've got it 🤞 -- I changed the "install addons" bit to refer to both kube-dns and coredns bc the linked page covers both, and we're still in this kube-dns + coredns halfway state with the doc.

neolit123 · 2018-06-12T13:23:48Z

/lgtm
thanks

k8s-ci-robot · 2018-06-12T13:23:48Z

@neolit123: you cannot LGTM your own PR.

In response to this:

/lgtm
thanks

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Bradamant3 · 2018-06-12T14:21:19Z

heh, so I'll do it for you, @neolit123

/lgtm
/approve

k8s-ci-robot · 2018-06-12T14:21:26Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bradamant3

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [Bradamant3]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

…8900) * dns-custom-namerserver: break down the page into mutliple sections This page is currently about kube-dns and is a bit outdated. Introduce the heading `# Customizing kube-dns`. Introduce a separate section about CoreDNS. * Copyedits, fix headings for customizing DNS Hey Lubomir, I coypedited pretty heavily because this workflow is so much easier for docs and because I'm trying to help improve everything touching kubeadm as much as possible. But there's one outstanding issue wrt headings and intro content: you can't add a heading 1 to a topic to do what you wanted to do. The page title in the front matter is rendered as a heading 1 and everything else has to start at heading 2. (We still need to doc this better in the docs contributing content, I know.) Instead, I think we need to rewrite the top-of-page intro content to explain better the relationship between kube-dns and CoreDNS. I'm happy to write something, but I thought I'd push this commit first so you can see what I'm doing. Hope it's all clear -- ping here or on Slack with any questions ~ Jennifer * Interim fix for talking about CoreDNS * Fix CoreDNS details

* Seperate priority and preemption (#8144) * Doc about PID pressure condition. (#8211) * Doc about PID pressure condition. Signed-off-by: Da K. Ma <[email protected]> * "so" -> "too" * Update version selector for 1.11 * StorageObjectInUseProtection is GA (#8291) * Feature gate: StorageObjectInUseProtection is GA Update feature gate reference for 1.11 * Trivial commit to re-trigger Netlify * CRIContainerLogRotation is Beta in 1.11 (#8665) * Seperate priority and preemption (#8144) * CRIContainerLogRotation is Beta in 1.11 xref: kubernetes/kubernetes#64046 * Bring StorageObjectInUseProtection feature to GA (#8159) * StorageObjectInUseProtection is GA (#8291) * Feature gate: StorageObjectInUseProtection is GA Update feature gate reference for 1.11 * Trivial commit to re-trigger Netlify * Bring StorageObjectInUseProtection feature to GA StorageObjectInUseProtection is Beta in K8s 1.10. It's brought to GA in K8s 1.11. * Fixed typo and added feature state tags. * Remove KUBE_API_VERSIONS doc (#8292) The support to the KUBER_API_VERSIONS environment variable is completely dropped (no deprecation). This PR removes the related doc in release-1.11. xref: kubernetes/kubernetes#63165 * Remove InitialResources from admission controllers (#8293) The feature (was experimental) is dropped in 1.11. xref: kubernetes/kubernetes#58784 * Remove docs related to in-tree support to GPU (#8294) * Remove docs related to in-tree support to GPU The in-tree support to GPU is completely removed in release 1.11. This PR removes the related docs in release-1.11 branch. xref: kubernetes/kubernetes#61498 * Update content updated by PR to Hugo syntax Signed-off-by: Misty Stanley-Jones <[email protected]> * Update the doc about extra volume in kubeadm config (#8453) Signed-off-by: Xianglin Gao <[email protected]> * Update CRD Subresources for 1.11 (#8519) * coredns: update notes in administer-cluster/coredns.md (#8697) CoreDNS is installed by default in 1.11. Add notes on how to install kube-dns instead. Update notes about CoreDNS->CoreDNS upgrades as in 1.11 the Corefile is retained. Add example on upgrading from kube-dns to CoreDNS. * kubeadm-alpha: CoreDNS related changes (#8727) Update note about CoreDNS feature gate. This change also updates a tab as a kubeadm sub-command will change. It looks for a new generated file: generated/kubeadm_alpha_phase_addon_coredns.md instead of: generated/kubeadm_alpha_phase_addon_kube-dns.md * Update cloud controller manager docs to beta 1.11 (#8756) * Update cloud controller manager docs to beta 1.11 * Use Hugo shortcode for feature state * kubeadm-upgrade: include new command `kubeadm upgrade diff` (#8617) Also: - Include note that this was added in 1.11. - Modify the note about upgrade guidance. * independent: update CoreDNS mentions for kubeadm (#8753) Give CoreDNS instead of kube-dns examples in: - docs/setup/independent/create-cluster-kubeadm.md - docs/setup/independent/troubleshooting-kubeadm.md * update 1.11 --server-print info (#8870) * update 1.11 --server-print info * Copyedit * Mark ExpandPersistentVolumes feature to beta (#8778) * Update version selector for 1.11 * Mark ExpandPersistentVolumes Beta xref: kubernetes/kubernetes#64288 * fix shortcode, add placeholder files to fix deploy failures (#8874) * declare ipvs ga (#8850) * kubeadm: update info about CoreDNS in kubeadm-init.md (#8728) Add info to install kube-dns instead of CoreDNS, as CoreDNS is the default DNS server in 1.11. Add notes that kubeadm config images can be used to list and pull the required images in 1.11. * kubeadm: update implementation-details.md about CoreDNS (#8829) - Replace examples from kube-dns to CoreDNS - Add notes about the CoreDNS feature gate status in 1.11 - Add note that the service name for CoreDNS is also called `kube-dns` * Update block device support for 1.11 (#8895) * Update block device support for 1.11 * Copyedits * Fix typo 'fiber channel' (#8957) Signed-off-by: Misty Stanley-Jones <[email protected]> * kubeadm-upgrade: add the 'node [config]' sub-command (#8960) - Add includes for the generated pages - Include placeholder generated pages * kubeadm-init: update the example for the MasterConfiguration (#8958) - include godocs link for MasterConfiguration - include example MasterConfiguration - add note that `kubeadm config print-default` can be used * kubeadm-config: include new commands (#8862) Add notes and includes for these new commands in 1.11: - kubeadm config print-default - kubeadm config migrate - kubeadm config images list - kubeadm config images pull Include placeholder generated files for the above. * administer-cluster/coredns: include more changes (#8985) It was requested that for this page a couple of methods should be outlined: - manual installation for CoreDNS explained at the Kubernetes section of the GitHub project for CoreDNS - installation and upgrade via kubeadm Make the above changes and also add a section "About CoreDNS". This commit also lowercases a section title. * Update CRD subresources doc for 1.11 (#8918) * Add docs for volume expansion and online resizing (#8896) * Add docs for volume expansion going beta * Copyedit * Address feedback * Update exec plugin docs with TLS credentials (#8826) * Update exec plugin docs with TLS credentials kubernetes/kubernetes#61803 implements TLS client credential support for 1.11. * Copyedit * More copyedits for clarification * Additional copyedit * Change token->credential * NodeRestriction admission prevents kubelet taint removal (#8911) * dns-custom-namerserver: break down the page into mutliple sections (#8900) * dns-custom-namerserver: break down the page into mutliple sections This page is currently about kube-dns and is a bit outdated. Introduce the heading `# Customizing kube-dns`. Introduce a separate section about CoreDNS. * Copyedits, fix headings for customizing DNS Hey Lubomir, I coypedited pretty heavily because this workflow is so much easier for docs and because I'm trying to help improve everything touching kubeadm as much as possible. But there's one outstanding issue wrt headings and intro content: you can't add a heading 1 to a topic to do what you wanted to do. The page title in the front matter is rendered as a heading 1 and everything else has to start at heading 2. (We still need to doc this better in the docs contributing content, I know.) Instead, I think we need to rewrite the top-of-page intro content to explain better the relationship between kube-dns and CoreDNS. I'm happy to write something, but I thought I'd push this commit first so you can see what I'm doing. Hope it's all clear -- ping here or on Slack with any questions ~ Jennifer * Interim fix for talking about CoreDNS * Fix CoreDNS details * PSP readOnly hostPath (#8898) * Add documentation for crictl (#8880) * Add documentation for crictl * Copyedit Signed-off-by: Misty Stanley-Jones <[email protected]> * Final copyedit * VolumeSubpathEnvExpansion alpha feature (#8835) * Note that Heapster is deprecated (#8827) * Note that Heapster is deprecated This notes that Heapster is deprecated, and migrates the relevant docs to talk about metrics-server or other solutions by default. * Copyedits and improvements Signed-off-by: Misty Stanley-Jones <[email protected]> * Address feedback * fix shortcode to troubleshoot deploy (#9057) * update dynamic kubelet config docs for v1.11 (#8766) * update dynamic kubelet config docs for v1.11 * Substantial copyedit * Address feedback * Reference doc for kubeadm (release-1.11) (#9044) * Reference doc for kubeadm (release-1.11) * fix shortcode to troubleshoot deploy (#9057) * Reference doc for kube-components (release-1.11) (#9045) * Reference doc for kube-components (release-1.11) * Update cloud-controller-manager.md * fix shortcode to troubleshoot deploy (#9057) * Documentation on lowercasing kubeadm init apiserver SANs (#9059) * Documentation on lowercasing kubeadm init apiserver SANs * fix shortcode to troubleshoot deploy (#9057) * Clarification in dynamic Kubelet config doc (#9061) * Promote sysctls to Beta (#8804) * Promote sysctls to Beta * Copyedits Signed-off-by: Misty Stanley-Jones <[email protected]> * Review comments * Address feedback * More feedback * kubectl reference docs for 1.11 (#9080) * Update Kubernetes API 1.11 ref docs (#8977) * Update v1alpha1 to v1beta1. * Adjust left nav for 1.11 ref docs. * Trim list of old ref docs. * Update Federation API ref docs for 1.11. (#9064) * Update Federation API ref docs for 1.11. * Add titles. * Update definitions.html * CRD versioning Public Documentation (#8834) * CRD versioning Public Documentation * Copyedit Signed-off-by: Misty Stanley-Jones <[email protected]> * Address feedback * More rewrites * Address feedback * Update main CRD page in light of versioning * Reorg CRD docs * Further reorg * Tweak title * CSI documentation update for raw block volume support (#8927) * CSI documetation update for raw block volume support * minor edits for "CSI raw block volume support" Some small grammar and style nits. * minor CSIBlockVolume edits * Update kubectl component ref page for 1.11. (#9094) * Update kubectl component ref page for 1.11. * Add title. Replace stevepe with username. * crd versioning doc: fix nits (#9142) * Update `DynamicKubeletConfig` feature to beta (#9110) xref: kubernetes/kubernetes#64275 * Documentation for dynamic volume limits based on node type (#8871) * add cos for storage limits * Update docs specific for aws and gce * fix some minor things * Update storage-limits.md * Add k8s version to feature-state shortcode * The Doc update for ScheduleDaemonSetPods (#8842) Signed-off-by: Da K. Ma <[email protected]> * Update docs related to PersistentVolumeLabel admission control (#9109) The said admission controller is disabled by default in 1.11 (kubernetes/kubernetes#64326) and scheduled to be removed in future release. * client exec auth: updates for 1.11 (#9154) * Updates HA kubeadm docs (#9066) * Updates HA kubeadm docs Signed-off-by: Chuck Ha <[email protected]> * kubeadm HA - Add stacked control plane steps * ssh instructions and some typos in the bash scripts Signed-off-by: Chuck Ha <[email protected]> * Fix typos and copypasta errors * Fix rebase issues * Integrate more changes Signed-off-by: Chuck Ha <[email protected]> * copyedits, layout and formatting fixes * final copyedits * Adds a sanity check for load balancer connection Signed-off-by: Chuck Ha <[email protected]> * formatting fixes, copyedits * fix typos, formatting * Document the Pod Ready++ feature (#9180) Closes: #9107 Xref: kubernetes/kubernetes#64057 * Mention 'KubeletPluginsWatcher' feature (#9177) * Mention 'KubeletPluginsWatcher' feature This feature is more developers oriented than users oriented, so simply mention it in the feature gate should be fine. In future, when the design doc is migrated from Google doc to the kubernetes/community repo, we can add links to it for users who want to dig deeper. Closes: #9108 Xref: kubernetes/kubernetes#63328, kubernetes/kubernetes#64605 * Copyedit * Amend dynamic volume list docs (#9181) The dynamic volume list feature has been documented but the feature gate related was not there yet. Closes: #9105 * Document for service account projection (#9182) This adds docs for the service account projection feature. Xref: kubernetes/kubernetes#63819, kubernetes/community#1973 Closes: #9102 * Update pod priority and preemption user docs (#9172) * Update pod priority and preemption user docs * Copyedit * Documentation on setting node name with Kubeadm (#8925) * Documentation on setting node name with Kubeadm * copyedit * Add kubeadm upgrade docs for 1.11 (#9089) * Add kubeadm upgrade docs for 1.11 * Initial docs review feedback * Add 1-11 to outline * Fix formatting on tab blocks * Move file to correct location * Add `kubeadm upgrade node config` step * Overzealous ediffing * copyedit, fix lists and headings * clarify --force flag for fixing bad state * Get TOML ready for 1.11 release * Blog post for 1.11 release (#9254) * Blog post for 1.11 release * Update 2018-06-26-kubernetes-1.11-release-announcement.md * Update 2018-06-26-kubernetes-1.11-release-announcement.md * Update 2018-06-26-kubernetes-1.11-release-announcement.md

k8s-ci-robot assigned Bradamant3 Jun 4, 2018

k8s-ci-robot added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Jun 4, 2018

k8s-ci-robot assigned rajansandeep Jun 4, 2018

k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 4, 2018

dns-custom-namerserver: break down the page into mutliple sections

5ffcf12

This page is currently about kube-dns and is a bit outdated. Introduce the heading `# Customizing kube-dns`. Introduce a separate section about CoreDNS.

k8s-ci-robot requested review from bowei and xiangpengzhao June 4, 2018 19:29

neolit123 force-pushed the dns-custom-nameservers branch from c79b839 to 5ffcf12 Compare June 4, 2018 19:29

k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 4, 2018

neolit123 mentioned this pull request Jun 4, 2018

document "CoreDNS by default in v1.11" kubernetes/kubeadm#843

Closed

11 tasks

mdlinville added this to the 1.11 milestone Jun 7, 2018

fturib reviewed Jun 7, 2018

View reviewed changes

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 8, 2018

zacharysarah added the Docs Review: Open Issues label Jun 12, 2018

Bradamant3 removed the Docs Review: Open Issues label Jun 12, 2018

Interim fix for talking about CoreDNS

17c6289

neolit123 commented Jun 12, 2018

View reviewed changes

Fix CoreDNS details

39c799f

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 12, 2018

k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 12, 2018

k8s-ci-robot merged commit 2d05bab into kubernetes:release-1.11 Jun 12, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

dns-custom-namerserver: break down the page into mutliple sections #8900

dns-custom-namerserver: break down the page into mutliple sections #8900

neolit123 commented Jun 4, 2018

k8sio-netlify-preview-bot commented Jun 4, 2018 •

edited

Loading

neolit123 commented Jun 4, 2018

rajansandeep commented Jun 4, 2018

fturib commented Jun 7, 2018

chrisohaver commented Jun 7, 2018 •

edited

Loading

Bradamant3 commented Jun 7, 2018

fturib left a comment

fturib Jun 7, 2018

fturib Jun 7, 2018

fturib Jun 7, 2018

fturib Jun 7, 2018

neolit123 commented Jun 7, 2018

Bradamant3 commented Jun 8, 2018

johnbelamaric commented Jun 8, 2018

neolit123 commented Jun 8, 2018

Bradamant3 commented Jun 8, 2018

Bradamant3 commented Jun 8, 2018

johnbelamaric commented Jun 8, 2018 via email

Bradamant3 commented Jun 12, 2018

neolit123 Jun 12, 2018

neolit123 Jun 12, 2018

Bradamant3 commented Jun 12, 2018

neolit123 commented Jun 12, 2018

k8s-ci-robot commented Jun 12, 2018

Bradamant3 commented Jun 12, 2018

k8s-ci-robot commented Jun 12, 2018

		CoreDNS is available as an option in Kubernetes starting from v1.9.
		It is currently a [GA feature](https://github.com/kubernetes/community/blob/master/keps/sig-network/0010-20180314-coredns-GA-proposal.md) and is on course to be [the default](https://github.com/kubernetes/community/blob/master/keps/sig-network/0012-20180518-coredns-default-proposal.md), replacing kube-dns.

dns-custom-namerserver: break down the page into mutliple sections #8900

dns-custom-namerserver: break down the page into mutliple sections #8900

Conversation

neolit123 commented Jun 4, 2018

k8sio-netlify-preview-bot commented Jun 4, 2018 • edited Loading

neolit123 commented Jun 4, 2018

rajansandeep commented Jun 4, 2018

fturib commented Jun 7, 2018

chrisohaver commented Jun 7, 2018 • edited Loading

Bradamant3 commented Jun 7, 2018

fturib left a comment

Choose a reason for hiding this comment

fturib Jun 7, 2018

Choose a reason for hiding this comment

fturib Jun 7, 2018

Choose a reason for hiding this comment

fturib Jun 7, 2018

Choose a reason for hiding this comment

fturib Jun 7, 2018

Choose a reason for hiding this comment

neolit123 commented Jun 7, 2018

Bradamant3 commented Jun 8, 2018

johnbelamaric commented Jun 8, 2018

neolit123 commented Jun 8, 2018

Bradamant3 commented Jun 8, 2018

Bradamant3 commented Jun 8, 2018

johnbelamaric commented Jun 8, 2018 via email

Bradamant3 commented Jun 12, 2018

neolit123 Jun 12, 2018

Choose a reason for hiding this comment

neolit123 Jun 12, 2018

Choose a reason for hiding this comment

Bradamant3 commented Jun 12, 2018

neolit123 commented Jun 12, 2018

k8s-ci-robot commented Jun 12, 2018

Bradamant3 commented Jun 12, 2018

k8s-ci-robot commented Jun 12, 2018

k8sio-netlify-preview-bot commented Jun 4, 2018 •

edited

Loading

chrisohaver commented Jun 7, 2018 •

edited

Loading