-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: Add static IP annotations for Calico and Kube-OVN #17
feat: Add static IP annotations for Calico and Kube-OVN #17
Conversation
template: | ||
metadata: | ||
annotations: | ||
cni.projectcalico.org/ipAddrs: '["$IP_ADDRESS"]' |
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.
Why not add them to templates rather than merging them on the fly?
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.
capch provides different template for each CNI, or user add it to template?
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.
We can use templates from capch accordingly by CNI flag?
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.
capch didn't provide templates for each CNI, in capch user have to download the common template and add annotations manually. knest did this automatically for Calico and Kube-ovn now.
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.
Then maybe we should add these templates in capch, and use them accordingly in knest?
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.
this will make capch have many templates(). at least 4 templates need to be added. they are cluster-template-cdi.yaml
+ calico/kube-ovn,cluster-template-cdi-internal.yaml
+ calico/kube-ovn. The design is if user use capch directly, they have to add annotations by themselves, if user use knest, knest did it.
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.
Yes, there will be many templates, but I think it's better we add annotations for CNIs we support than let user add them since it's not a trivial task.
No description provided.