-
Notifications
You must be signed in to change notification settings - Fork 80
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
Add cni path config in whereabouts to make it work in k3s #426
Add cni path config in whereabouts to make it work in k3s #426
Conversation
@@ -46,5 +46,9 @@ tolerations: | |||
|
|||
affinity: {} | |||
|
|||
cni_conf: |
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.
does it have to be cni_conf
? The convention is to use camelCase in yaml, not underscores. Maybe just cni
or cniConf
?
cni_conf: | |
cni: |
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.
good point! I just copied what Multus is using
2066f2f
to
a91a23a
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.
(nit) doesn't affect the functionality, but should we also bump the whereabouts packageVersion
too?
yeah, I think we should bump both the chart, and the subchart? |
Signed-off-by: Manuel Buil <mbuil@suse.com>
a91a23a
to
4b879a5
Compare
The CNI binaries and CNI config files do not use the default paths in k3s, therefore, we need a way to configure those parameters if we want to use whereabouts
Multus version must be incremented because it embeds whereabouts