Skip to content

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

Closed
wants to merge 1 commit into from

Conversation

jboxman
Copy link
Contributor

@jboxman jboxman commented Jun 20, 2020

@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.

@jboxman
Copy link
Contributor Author

jboxman commented Jul 16, 2020

@dougbtv, do we know what CNI plug-ins route-override is compatible with?

Thanks.

@jboxman jboxman force-pushed the multus-add-route-override branch from b92c017 to 1be2dad Compare July 23, 2020 17:05
@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 23, 2020
@jboxman
Copy link
Contributor Author

jboxman commented Sep 22, 2020

This overlaps with declarative configurations for creating multiple networks. It might be best to do both.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 21, 2020
@jboxman
Copy link
Contributor Author

jboxman commented Dec 21, 2020

/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 21, 2020
@vikram-redhat
Copy link
Contributor

@jboxman is this still valid? If not, can you close it?

@openshift-ci
Copy link

openshift-ci bot commented May 6, 2021

@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.

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 6, 2021
@jboxman
Copy link
Contributor Author

jboxman commented May 6, 2021

@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.

@jboxman jboxman assigned jboxman-rh and unassigned jboxman Oct 29, 2021
@jboxman jboxman closed this Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants