Skip to content

Conversation

@tnierman
Copy link
Member

https://issues.redhat.com/browse/SREP-1831


Modifies the label used by the suggested watch command to print all (current and new) control-plane instances when watching control-plane scale-up/down processes.

fmt.Println("Service log sent successfully. Use the following command to track progress of the resize:")
fmt.Println()
fmt.Println(`watch -d 'oc get machines -n openshift-machine-api -l machine.openshift.io/cluster-api-machine-role=master && oc get nodes -l node-role.kubernetes.io/control-plane'`)
fmt.Println(`watch -d 'oc get machines -n openshift-machine-api -l machine.openshift.io/cluster-api-machine-role=master && oc get nodes -l node-role.kubernetes.io/master'`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't CPMS switch to "control-plane" at some point? Won't this not work for "newer" instances?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking to our other codebases in the openshift org, it seems like critical components such as etcd still rely on this label as of the 4.22 branch: https://github.com/openshift/cluster-etcd-operator/blob/release-4.22/pkg/cmd/render/certs.go#L50

It's not exactly the same thing, but the enhancements repo also specifies the role.kubernetes.io/master taint is still the de-facto source-of-truth, with no plans to switch to a role.kubernetes.io/control-plane equivalent.

From testing on a 4.17.z cluster, I'm happy to report that the role.kubernetes.io/master label does select all instances correctly, while the role.kubernetes.io/control-plane one only returns the newly made control-plane nodes

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha! So the new nodes have both labels? If so, this looks good to me.

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 21, 2025

@tnierman: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 21, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joshbranham, tnierman

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 21, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 4c5df7e into openshift:master Sep 21, 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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants