Skip to content

Conversation

@dparalen
Copy link
Contributor

Current implementation never considers the "kube-router.io/pod-cidr"
annotation when creating an ipset for the node pod network CIDR.
The Node.Spec.PodCIDR is always used instead.

This patch prefers the annotation PodCIDR over the Node.Spec.PodCIDR

Current implementation never considers the "kube-router.io/pod-cidr"
annotation when creating an ipset for the node pod network CIDR.
The Node.Spec.PodCIDR is always used instead.

This patch prefers the annotation PodCIDR over the Node.Spec.PodCIDR
@dparalen
Copy link
Contributor Author

Hi all,
just to add a bit more context, I've run into an K8s node pod CIDR API issue the other day, that manifests in kube-router as the following error log:

E0425 13:34:14.081520    3889 network_routes_controller.go:262] Error synchronizing ipsets: Failed to sync Pod Subnets ipset: ipset v6.34: Syntax error: cannot parse : resolving to IPv4 address failed

After a bit of debugging, it turns out the issue is the empty string from the undefined value of Node.Spec.PodCIDR. This happens inspite of the node being annotaded with kube-router.io/pod-cidr.

@murali-reddy
Copy link
Member

thanks @dparalen LGTM

@murali-reddy murali-reddy merged commit 7181d6f into cloudnativelabs:master Apr 25, 2019
@dparalen
Copy link
Contributor Author

@murali-reddy thanks for a very quick response!

@dparalen dparalen deleted the prefer_annotation_node_pod_cidr branch April 25, 2019 18:31
mk01 pushed a commit to mk01/kube-router-ipv6 that referenced this pull request Mar 12, 2020
Current implementation never considers the "kube-router.io/pod-cidr"
annotation when creating an ipset for the node pod network CIDR.
The Node.Spec.PodCIDR is always used instead.

This patch prefers the annotation PodCIDR over the Node.Spec.PodCIDR

(cherry picked from commit 7181d6f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants