From 85e0fb32e64da9764e697171515606f178316a6c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20Vorburger=20=E2=9B=91=EF=B8=8F?= Date: Tue, 26 Mar 2019 11:51:19 +0100 Subject: [PATCH] clarify that kubespray now supports kubeadm (fixes #4089) (#4366) --- docs/comparisons.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/comparisons.md b/docs/comparisons.md index e731c8433..06a378b71 100644 --- a/docs/comparisons.md +++ b/docs/comparisons.md @@ -19,7 +19,9 @@ on. Had it belonged to the new [operators world](https://coreos.com/blog/introdu it may have been named a "Kubernetes cluster operator". Kubespray however, does generic configuration management tasks from the "OS operators" ansible world, plus some initial K8s clustering (with networking plugins included) and -control plane bootstrapping. Kubespray [strives](https://github.com/kubernetes-sigs/kubespray/issues/553) -to adopt kubeadm as a tool in order to consume life cycle management domain -knowledge from it and offload generic OS configuration things from it, which -hopefully benefits both sides. +control plane bootstrapping. + +Kubespray supports `kubeadm` for cluster creation since v2.3 +(and deprecated non-kubeadm deployment starting from v2.8) +in order to consume life cycle management domain knowledge from it +and offload generic OS configuration things from it, which hopefully benefits both sides.