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
kube_network_node_prefix is not getting applied to Calico #11102
Comments
kube_network_node_prefix is not used by calico, because calico dynamically assign ip block to node (at least in the default ipam mode used by kubespray). see #9843 (comment) , and the rest of the discussion |
I got that , and explicitly set |
I got that , and explicitly set `calico_pool_blocksize` but then maybe we should remove the comment `# add default ippool blockSize (defaults kube_network_node_prefix)` from `k8s-net-calico.yml`
That's in the inventory sample, right ? :sigh: That stuff is never in sync, I can't wait to get rid of it X^X
|
there you go |
What happened?
I have a Calico configuration and used kube_network_node_prefix to also pass to Calico but after installation I realized Calico role is not using the default (kube_network_node_prefix) value and passed /26 value
What did you expect to happen?
I was expecting the calico to default to kube_network_node_prefix
How can we reproduce it (as minimally and precisely as possible)?
run kubespray with kube_network_node_prefix set and calico_pool_blocksize commented.
OS
Debian 12
Version of Ansible
ansible [core 2.15.8]
Version of Python
Python 3.10.12
Version of Kubespray (commit)
used v2.24.1 docker image
Network plugin used
calico
Full inventory with variables
master01 | SUCCESS => {
"msg": "Hello world!"
}
master02 | SUCCESS => {
"msg": "Hello world!"
}
master03 | SUCCESS => {
"msg": "Hello world!"
}
worker01 | SUCCESS => {
"msg": "Hello world!"
}
worker02 | SUCCESS => {
"msg": "Hello world!"
}
Command used to invoke ansible
ansible-playbook -i inventory/ansible.hosts -u abc --become --become-user=root cluster.yml -K
Output of ansible run
Anything else we need to know
.
The text was updated successfully, but these errors were encountered: