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

Determine which "start" flags to support in "node" #7366

Closed
sharifelgamal opened this issue Apr 2, 2020 · 2 comments · Fixed by #17909
Closed

Determine which "start" flags to support in "node" #7366

sharifelgamal opened this issue Apr 2, 2020 · 2 comments · Fixed by #17909
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

@sharifelgamal
Copy link
Collaborator

We should figure out which minikube start parameters to support for minikube node add and minikube node start
@sharifelgamal sharifelgamal added the co/multinode Issues related to multinode clusters label Apr 2, 2020
@medyagh medyagh added the triage/discuss Items for discussion label Apr 8, 2020
@sharifelgamal sharifelgamal mentioned this issue Apr 9, 2020
Open
13 tasks
@sharifelgamal sharifelgamal added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/feature Categorizes issue or PR as related to a new feature. labels Apr 15, 2020
@tstromberg tstromberg changed the title minikube node start params Determine which "start" flags to support in "node" May 5, 2020
@tstromberg tstromberg removed the triage/discuss Items for discussion label Jun 24, 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-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 Oct 21, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 20, 2020
@sharifelgamal sharifelgamal added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Dec 2, 2020
@spowelljr spowelljr added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Mar 24, 2021
@rmsilva1973 rmsilva1973 mentioned this issue Sep 3, 2023
Open
@prezha prezha mentioned this issue Jan 7, 2024
Merged
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support multi-control plane - HA clusters prezha/minikube
6 participants
@tstromberg @medyagh @k8s-ci-robot @sharifelgamal @fejta-bot @spowelljr