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
Fix k8s podCIDRs for vagrant deployment #22786
Fix k8s podCIDRs for vagrant deployment #22786
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. I think the changes need only be scoped to contrib/vagrant
.
8a37f02
to
8745e2e
Compare
This comment was marked as resolved.
This comment was marked as resolved.
cdd2eff
to
826fc94
Compare
@julianwiedmann Could you re-review to check if your comments have been addressed? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @romanspb80 , thanks! Besides the IPv6 inconsistency in the change (as noted below), a more general remark - we want these CIDRs to end up looking identical to what gets passed to
cilium/contrib/vagrant/start.sh
Lines 332 to 333 in 80af06e
cilium_operator_options+=" --cluster-pool-ipv4-cidr=10.${master_ipv4_suffix}.0.0/16" | |
cilium_operator_options+=" --cluster-pool-ipv6-cidr=fd04::/104" |
Right now the per-node CIDR size gets auto-sized there, but it can be configured with --cluster-pool-ipv4-mask-size
.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
7ffaf03
to
befac67
Compare
This patch makes podCIDRs of k8s Node and CiliumNode consistent: vagrant@k8s1:~/go/src/github.com/cilium/cilium$ kubectl get nodes k8s1 -o yaml apiVersion: v1 kind: Node metadata: ... spec: podCIDR: 10.11.0.0/24 podCIDRs: - 10.11.0.0/24 - fd04::/112 ... vagrant@k8s1:~/go/src/github.com/cilium/cilium$ kubectl get ciliumnodes.cilium.io -o yaml apiVersion: v1 items: - apiVersion: cilium.io/v2 kind: CiliumNode ... spec: ... ipam: podCIDRs: - 10.11.0.0/24 - fd04::/112 ... Fixes: cilium#19594 Signed-off-by: Roman Ptitcyn <romanspb@yahoo.com>
befac67
to
b85a883
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @romanspb80 !
Think we're good to go - this is devVM-only, so the CI won't do us any good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested this locally.
Thanks guys! |
This patch makes podCIDRs of k8s Node and CiliumNode consistent: vagrant@k8s1:~/go/src/github.com/cilium/cilium$ kubectl get nodes k8s1 -o yaml apiVersion: v1
kind: Node
metadata:
...
spec:
podCIDR: 10.11.0.0/24
podCIDRs:
vagrant@k8s1:~/go/src/github.com/cilium/cilium$ kubectl get ciliumnodes.cilium.io -o yaml apiVersion: v1
items:
Fixes: #19594
Signed-off-by: Roman Ptitcyn romanspb@yahoo.com