Skip to content

feat: Support for auto-detecting nodes to add.#2560

Merged
kubesphere-prow[bot] merged 1 commit into
kubesphere:feature-gitopsfrom
redscholar:feature
May 12, 2025
Merged

feat: Support for auto-detecting nodes to add.#2560
kubesphere-prow[bot] merged 1 commit into
kubesphere:feature-gitopsfrom
redscholar:feature

Conversation

@redscholar

@redscholar redscholar commented May 12, 2025

Copy link
Copy Markdown
Contributor

What type of PR is this?

/kind feature

What this PR does / why we need it:

Support for auto-detecting nodes to add.
There are two executors available for adding nodes:

  1. kk add nodes
    This will add all nodes listed in the inventory that are not yet installed in the cluster.

  2. kk add nodes --control-plane node1,node2 --worker node1,node2
    This will only add the specified nodes to the cluster as control-plane or worker nodes.
    Ensure their connection details are provided in the inventory's hosts file.

Which issue(s) this PR fixes:

Fixes #
Replenish: #2557

Special notes for reviewers:

Does this PR introduced a user-facing change?

Support for auto-detecting nodes to ad

Additional documentation, usage docs, etc.:


@kubesphere-prow kubesphere-prow Bot added kind/feature Categorizes issue or PR as related to a new feature. do-not-merge/release-note-label-needed labels May 12, 2025
@kubesphere-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: redscholar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubesphere-prow kubesphere-prow Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. release-note and removed do-not-merge/release-note-label-needed labels May 12, 2025
Signed-off-by: joyceliu <joyceliu@yunify.com>
@sonarqubecloud

Copy link
Copy Markdown

@pixiake

pixiake commented May 12, 2025

Copy link
Copy Markdown
Collaborator

/lgtm

@kubesphere-prow kubesphere-prow Bot added the lgtm Indicates that a PR is ready to be merged. label May 12, 2025
@kubesphere-prow

Copy link
Copy Markdown

LGTM label has been added.

DetailsGit tree hash: e366fac46aaa1121cfb2289f9b38440fe52165ad

@kubesphere-prow kubesphere-prow Bot merged commit 9a672ad into kubesphere:feature-gitops May 12, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants