You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2024. It is now read-only.
If the maintainers agree with the feature as described here, I intend to submit a Pull Request myself.1
Proposal:
I want to add error override labels for a CNI plugin.
Obviously, it must run as root, have host network and NET_ADMIN capability.
The plugin itself is a daemon set, so it has no fixed pod name, so I cannot override errors on the pod level (or, at least, do not understand how).
The pod has several containers, so adding these labels at container level is tedious.
I hope for CNI plugins it will be fixed with #275 , but there might be other daemonsets which needs auditing (logging, etc).
1This is the quickest way to get a new feature! We reserve the right to close feature requests, even ones we like, if the proposer does not intend to contribute to the feature and it doesn't fit in our current roadmap.
The text was updated successfully, but these errors were encountered:
ISSUE TYPE
FEATURE IDEA
Proposal:
I want to add error override labels for a CNI plugin.
Obviously, it must run as root, have host network and NET_ADMIN capability.
The plugin itself is a daemon set, so it has no fixed pod name, so I cannot override errors on the pod level (or, at least, do not understand how).
The pod has several containers, so adding these labels at container level is tedious.
I hope for CNI plugins it will be fixed with #275 , but there might be other daemonsets which needs auditing (logging, etc).
1 This is the quickest way to get a new feature! We reserve the right to close feature requests, even ones we like, if the proposer does not intend to contribute to the feature and it doesn't fit in our current roadmap.
The text was updated successfully, but these errors were encountered: