Skip to content
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

[BUG] Dynamic update of routes to pod using whereabouts IPAM #382

Open
rajubi1981 opened this issue Sep 5, 2023 · 0 comments
Open

[BUG] Dynamic update of routes to pod using whereabouts IPAM #382

rajubi1981 opened this issue Sep 5, 2023 · 0 comments

Comments

@rajubi1981
Copy link

Describe the bug

  • We have installed whereabouts as IPAM.
  • We have configured the routes to be configured as put below.

apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
name: ipvlan-media
spec:
config: '{
"cniVersion": "0.3.1",
"plugins": [
{
"type": "ipvlan",
"master": "eth1",
"mtu": 1500,
"ipam": {
"type": "whereabouts",
"range": "10.211.0.0/20",
"range_start": "10.2101.2.221",
"range_end": "10.2101.2.229",
"routes": [{"dst":"10.205.0.0/24","gw":"10.205.0.254"},{"dst":"0.0.0.0/0"}],
"gateway": "10.211.0.254"
}
},
{
"type": "sbr"
}
]
}'

  • The above mentioned routes will be observed in the pod which uses this NAD.
  • Now we add / remove routes in the NAD and update the NAD.
  • The newly added routes are not reflected in the pod unless we redeploy the pod.

Expected behavior
The newly added routes should be reflected in the pod without redeployment

To Reproduce
Steps to reproduce the behavior:
1.
2.
3.

Environment:

  • Whereabouts version : latest
  • Kubernetes version (use kubectl version): v1.24.6
  • Network-attachment-definition: Mentioned
  • Whereabouts configuration (on the host): N/A
  • OS (e.g. from /etc/os-release): Rocky Linux 8.7
  • Kernel (e.g. uname -a): Linux master-1 4.18.0-425.10.1.el8_7.x86_64 Exclude range #1 SMP Thu Jan 12 16:32:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  • Others: N/A

Additional info / context
Add any other information / context about the problem here.

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

No branches or pull requests

1 participant