New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
specifying node-cidr-mask-size as a controllerManagerExtra arg did not take precedence #724
Comments
still present in 1.9.6. It should really be just an option under |
@tmjd I've worked around it by moving the Modifying your original example, it becomes:
This workaround is essentially circumventing kubeadm's I doesn't appear that kubeadm uses the Would still prefer to be able to override the node cidr mask size in a more supported fashion though. |
…drmasksize Automatic merge from submit-queue (batch tested with PRs 61705, 61609, 62103, 62113, 62115). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Support overriding the --node-cidr-mask-size arg passed to kube-controller-manager Fixes: kubernetes/kubeadm#724 **Release note**: ```release-note kubeadm config can now override the Node CIDR Mask Size passed to kube-controller-manager. ```
@tmjd Fix should land in next kubeadm release from master. |
What is the status on this?
The Issue is still occurring here. |
What keywords did you search in kubeadm issues before filing this one?
controllerManagerExtraArgs, node-cidr-mask-size
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
kubeadm version (use
kubeadm version
): v1.9.3Environment:
kubectl version
): v1.9.3uname -a
): Linux k8s-master 4.13.16-coreos-r2 kubeadm join on slave node fails preflight checks #1 SMP Wed Dec 6 04:27:34 UTC 2017 x86_64 Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz GenuineIntel GNU/LinuxWhat happened?
I was specifying
node-cidr-mask-size
in a kubeadm config file undercontrollerManagerExtraArgs
to set the flag. kube-controller-manager was started with 2 instances of--node-cidr-mask-size
being passed to it. The 2nd instance was the default that kubeadm adds and overrode the value I was attempting to set.What you expected to happen?
kube-controller-manager should have been started with one instance of
--node-cidr-mask-size
or at least the one I specified would be the 2nd so that it would take precedence.How to reproduce it (as minimally and precisely as possible)?
kubeadm init --config=myconfig.yaml
with the following as the contents of the file myconfig.yamlAnything else we need to know?
This was an issue for me when trying to use kubeadm to setup an IPv6 cluster and specify a podSubnet.
The text was updated successfully, but these errors were encountered: