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.

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

Prevent NetworkManager from managing the kube-ipvsX interface #6950

Closed
MarkSymsCtx opened this issue Nov 25, 2020 · 1 comment · Fixed by #7315
Closed

Prevent NetworkManager from managing the kube-ipvsX interface #6950

MarkSymsCtx opened this issue Nov 25, 2020 · 1 comment · Fixed by #7315
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@MarkSymsCtx
Copy link

What would you like to be added:
Add play for kube-ipvsX to prevent networkManager from managing the kube-ipvsX interface(s), similar to what is done for calico interfaces.

Why is this needed:
Otherwise NetworkManager sets the interface to down and no traffic passes.

@MarkSymsCtx MarkSymsCtx added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 25, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants