From f3f6b39bbed0c61670d2288316f4f593eb1d8801 Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Wed, 20 Jun 2018 15:39:09 +0300 Subject: [PATCH] kubeadm: add feature state in implementation-details.md (#9151) implementation-details.md is outdated for k8s 1.11. Add feature state that this page applies to k8s 1.10. The page should be updated for k8s 1.11 in a later stage in the release cycle. --- .../reference/setup-tools/kubeadm/implementation-details.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md b/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md index 99ca404fdb..38dc52bfb3 100644 --- a/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md +++ b/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md @@ -8,6 +8,9 @@ content_template: templates/concept weight: 100 --- {{% capture overview %}} + +{{< feature-state for_k8s_version="v1.10" state="stable" >}} + `kubeadm init` and `kubeadm join` together provides a nice user experience for creating a best-practice but bare Kubernetes cluster from scratch. However, it might not be obvious _how_ kubeadm does that.