From 192e4cb431f4a7110302bd7561c5ae9c4cf5509d Mon Sep 17 00:00:00 2001 From: priitliivak Date: Fri, 28 Sep 2018 10:56:37 +0300 Subject: [PATCH] Changes for the comments under PR #19 --- README.md | 4 ++++ defaults/main.yml | 3 +-- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e93d6b2..a39be0c 100644 --- a/README.md +++ b/README.md @@ -31,6 +31,10 @@ Whether the particular server will serve as a Kubernetes `master` (default) or ` Extra args to pass to `kubelet` during startup. E.g. to allow `kubelet` to start up even if there is swap is enabled on your server, set this to: `"--fail-swap-on=false"`. Or to specify the node-ip advertised by `kubelet`, set this to `"--node-ip={{ ansible_host }}"`. + kubernetes_kubeadm_init_extra_opts: "" + +Extra args to pass to `kubeadm init` during K8s control plane initialization. E.g. to specify extra Subject Alternative Names for API server certificate, set this to: `"--apiserver-cert-extra-sans my-custom.host"` + kubernetes_allow_pods_on_master: True Whether to remove the taint that denies pods from being deployed to the Kubernetes master. If you have a single-node cluster, this should definitely be `True`. Otherwise, set to `False` if you want a dedicated Kubernetes master which doesn't run any other pods. diff --git a/defaults/main.yml b/defaults/main.yml index cd59427..d11ef3b 100644 --- a/defaults/main.yml +++ b/defaults/main.yml @@ -12,8 +12,7 @@ kubernetes_packages: kubernetes_role: master kubernetes_kubelet_extra_args: "" -# Any additional options for kubeadm init -kubeadm_init_opts: "" +kubernetes_kubeadm_init_extra_opts: "" kubernetes_allow_pods_on_master: True kubernetes_enable_web_ui: True