Skip to content
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.

Sign up for GitHub

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

Jump to bottom

auto egress IP vs joined namespaces #18852

Closed
danwinship opened this issue Mar 6, 2018 · 3 comments
Closed

auto egress IP vs joined namespaces #18852

danwinship opened this issue Mar 6, 2018 · 3 comments
Assignees
@danwinship
Labels
component/networking kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/networking

Comments

@danwinship
Copy link
Contributor

Auto-egress-IP has the same problems with multitenant joined namespaces as EgressNetworkPolicy and multicast do (auto-egress-IP is configured per-Namespace but implemented per-VNID), so it needs to have the same fail-when-applied-to-joined-namespaces behavior.
@danwinship danwinship added kind/bug Categorizes issue or PR as related to a bug. component/networking sig/networking labels Mar 6, 2018
@danwinship danwinship self-assigned this Mar 6, 2018
@danwinship danwinship mentioned this issue Mar 6, 2018
Merged
@openshift-bot
Copy link
Contributor

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 Jun 4, 2018
@danwinship
Copy link
Contributor Author

/remove-lifecycle stale
/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 Jun 4, 2018
@danwinship
Copy link
Contributor Author

sdn is no longer in this repo, and this bug is unlikely to be fixed since it only applies to the deprecated multitenant plugin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danwinship danwinship

Labels
component/networking kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/networking
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@danwinship @openshift-bot @openshift-ci-robot