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

talosctl bootstrap should deny more than a single node #5636

Closed
smira opened this issue May 25, 2022 · 0 comments · Fixed by #5734
Closed

talosctl bootstrap should deny more than a single node #5636

smira opened this issue May 25, 2022 · 0 comments · Fixed by #5734
Assignees

Comments

@smira
Copy link
Member

smira commented May 25, 2022

Feature Request

If a user does e.g. talosctl -n CP-IP1,CP-IP2,CP-IP3 bootstrap, it should not allow bootstrapping more than a single node.

Description

sauterp pushed a commit to sauterp/talos that referenced this issue Jun 10, 2022
Previously talosctl would accept multiple nodes for the bootstrap
command which is a strictly single-node operation. Talosctl will abort
the bootstrap command if more than one node is specified either as a
command-line flag or in talosconfig.

Fixes siderolabs#5636

Signed-off-by: Philipp Sauter <[email protected]>
sauterp pushed a commit to sauterp/talos that referenced this issue Jun 10, 2022
Previously talosctl would accept multiple nodes for the bootstrap
command which is a strictly single-node operation. Talosctl will abort
the bootstrap command if more than one node is specified either as a
command-line flag or in talosconfig.

Fixes siderolabs#5636

Signed-off-by: Philipp Sauter <[email protected]>
smira pushed a commit to smira/talos that referenced this issue Jun 21, 2022
Previously talosctl would accept multiple nodes for the bootstrap
command which is a strictly single-node operation. Talosctl will abort
the bootstrap command if more than one node is specified either as a
command-line flag or in talosconfig.

Fixes siderolabs#5636

Signed-off-by: Philipp Sauter <[email protected]>
(cherry picked from commit 7a11b4d)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants