-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
CALICO-IPAM not using NODENAME nor FELIX_FELIXHOSTNAME #826
Comments
Hm. It's not Felix that writes those values into etcd, rather it's the calico-ipam CNI plugin. What does your CNI config look like? Does it have a |
Thanks for the clarification/precision. My CNI config:
|
…-release-v3.20 [release-v3.20] Semaphore Auto Pin Update
When a pod is created on a cluster with minions having multiple interface. Calico/Felix does not use NODENAME / FELIX_FELIXHOSTNAME but still use "get_host_by_name()" in order to write the key in etcd.
Expected Behavior
In etcd the key written should be in the form:
/calico/ipam/v2/host//ipv4/block/192.168.3.128-26
Now it is still in the form:
/calico/ipam/v2/host/<sys.gethostbyname()>/ipv4/block/192.168.3.128-26
calico/felix should use NODENAME or FELIX_FELIXHOSTNAME when precised.
Current Behavior
The result is that only /32 route to pod is advertised and not the right /26
host-local tested and calico-ipam node tested.
Possible Solution
calico/felix should use NODENAME or FELIX_FELIXHOSTNAME when precised.
Steps to Reproduce (for bugs)
Context
Only /32 pod route were advertised into the cluster. Not the /26.
Your Environment
The text was updated successfully, but these errors were encountered: