-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Multi-node Enhancements #7538
Labels
co/multinode
Issues related to multinode clusters
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
Closed
still in progress :) |
An absolutely feat! ❤ |
This was referenced Dec 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
co/multinode
Issues related to multinode clusters
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
This is the meta issue tracking everything that needs to happen to get our multi-node feature more stable and no longer experimental.
Required for GA:
minikube profile
commands need to not be broken (Add number of nodes for cluster inminikube profile list
#6780)Nice to have:
minikube node start/add
should respect relevantminikube start
parameters (Determine which "start" flags to support in "node" #7366)Please add any other relevant issues that I might have missed.
The text was updated successfully, but these errors were encountered: