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

Use a CNI by default in minikube (flannel?) #6094

Closed
tstromberg opened this issue Dec 16, 2019 · 4 comments
Closed

Use a CNI by default in minikube (flannel?) #6094

tstromberg opened this issue Dec 16, 2019 · 4 comments
Assignees
@sharifelgamal
Labels
area/cni CNI support help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. 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. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@tstromberg
Copy link
Contributor

For consistency and to prepare for multi-node.
@tstromberg tstromberg added area/cni CNI support kind/feature Categorizes issue or PR as related to a new feature. long-term-support Long-term support issues that can't be fixed in code labels Dec 16, 2019
@tstromberg
Copy link
Contributor Author

/cc @sharifelgamal

@tstromberg tstromberg mentioned this issue Dec 16, 2019
Closed
@tstromberg tstromberg added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Dec 16, 2019
@sharifelgamal
Copy link
Collaborator

Related: #94

@sharifelgamal sharifelgamal self-assigned this Dec 16, 2019
@tstromberg tstromberg added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed long-term-support Long-term support issues that can't be fixed in code labels Dec 19, 2019
@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-testing, kubernetes/test-infra and/or fejta.
/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 Mar 18, 2020
@tstromberg
Copy link
Contributor Author

Closed in preference to #7459

IMHO, there is little sense in running a CNI for single-node use.

@afbjorklund afbjorklund mentioned this issue Aug 8, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sharifelgamal sharifelgamal

Labels
area/cni CNI support help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. 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. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tstromberg @k8s-ci-robot @sharifelgamal @fejta-bot