-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Include route-override chained CNI plug-in #23108
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
Conversation
@dougbtv, do we know what CNI plug-ins route-override is compatible with? Thanks. |
b92c017
to
1be2dad
Compare
This overlaps with declarative configurations for creating multiple networks. It might be best to do both. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/lifecycle frozen |
@jboxman is this still valid? If not, can you close it? |
@jboxman: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@vikram-redhat, it's relevant to multiple networks, but the necessary background content does not exist. It's one of the focus areas for closing networking documentation gaps, yet to be realized. |
@dougbtv,
route-override
fits best as a new topic. Once this is complete, it will be included in the TOC.Will there be additional chained CNI plug-ins? Eventually this may need to morph into more expansive content if so.