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

Create Node operations for multinode #6300

Closed
sharifelgamal opened this issue Jan 13, 2020 · 0 comments · Fixed by #6556
Closed

Create Node operations for multinode #6300

sharifelgamal opened this issue Jan 13, 2020 · 0 comments · Fixed by #6556
Assignees
Labels
co/multinode Issues related to multinode clusters kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@sharifelgamal
Copy link
Collaborator

sharifelgamal commented Jan 13, 2020

minikube node add
minikube node start
minikube node stop
minikube node delete

Implement those 4 operations and all the config nonsense that goes along with it.

Make sure to fix MachineConfig so we can refactor all the node specific stuff.

ref #94

@sharifelgamal sharifelgamal self-assigned this Jan 13, 2020
@medyagh medyagh added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/feature Categorizes issue or PR as related to a new feature. labels Jan 22, 2020
@sharifelgamal sharifelgamal added the co/multinode Issues related to multinode clusters label Feb 5, 2020
@tstromberg tstromberg added this to the v1.8.0 milestone Feb 5, 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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants