OCPBUGS-82584: Add labelSelector to MachineSet status for scale subresource

[RadekManak]

Summary

MachineSet already advertises a scale subresource with labelSelectorPath: .status.labelSelector, but the API/schema does not define that status field.

• adds status.labelSelector to machine.openshift.io/v1beta1 MachineSetStatus

The paired openshift/machine-api-operator#1490 change populates status.labelSelector from spec.selector during MachineSet status reconciliation so the /scale subresource can expose Scale.status.selector for HPA/KEDA-style consumers.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@RadekManak: This pull request references Jira Issue OCPBUGS-82584, which is invalid:

• expected the bug to target the "5.0.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

MachineSet already advertises a scale subresource with labelSelectorPath: .status.labelSelector, but the API/schema does not define that status field.

• adds status.labelSelector to machine.openshift.io/v1beta1 MachineSetStatus

The paired openshift/machine-api-operator#1490 change populates status.labelSelector from spec.selector during MachineSet status reconciliation so the /scale subresource can expose Scale.status.selector for HPA/KEDA-style consumers.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hello @RadekManak! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

An optional LabelSelector field (type string) was added to MachineSetStatus in machine/v1beta1/types_machineset.go (JSON: labelSelector,omitempty, validation: MinLength=0, MaxLength=4096). It represents the serialized label selector for the MachineSet's machines and is exposed via the scale subresource as status.selector. The field remains unset until the controller reconciles spec.selector into status.labelSelector. No other spec or status fields or control-flow logic were changed.

🚥 Pre-merge checks | ✅ 9 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Test Structure And Quality	❓ Inconclusive	PR appears to contain only schema field additions to MachineSetStatus type with no Ginkgo test code modifications identified.	Clarify if PR includes any Ginkgo test code changes requiring custom check review for test quality standards.

✅ Passed checks (9 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a labelSelector field to MachineSet status for the scale subresource, matching the changeset.
Description check	✅ Passed	The description is directly related to the changeset, explaining why the labelSelector field is being added to MachineSetStatus and its purpose for the scale subresource.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names	✅ Passed	PR contains no Ginkgo test code, only static type definition field additions. No test names introduced or modified.
Microshift Test Compatibility	✅ Passed	This pull request is not applicable to the MicroShift Test Compatibility check because it does not add any new Ginkgo e2e tests. The change is purely an API schema modification that adds a LabelSelector field to the MachineSetStatus type in the machine API.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The custom check evaluates SNO compatibility for new Ginkgo e2e tests. This PR only adds an optional LabelSelector field to MachineSetStatus type with no new test code, making the check not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR adds only a LabelSelector field to MachineSetStatus struct with no scheduling constraints, pod affinity rules, or controller logic.
Ote Binary Stdout Contract	✅ Passed	This PR modifies only an API type definition file adding a field to MachineSetStatus struct. The OTE Binary Stdout Contract applies to test binaries and executable code, not pure type definitions.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR adds a LabelSelector field to MachineSetStatus type, not Ginkgo e2e tests, so the check does not apply.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[RadekManak]

/jira refresh

[openshift-ci-robot]

@RadekManak: This pull request references Jira Issue OCPBUGS-82584, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@RadekManak: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/verify-hypershift-integration	53cb6e6	link	true	/test verify-hypershift-integration
ci/prow/verify	53cb6e6	link	true	/test verify

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.

[everettraven]

/lgtm

[openshift-merge-bot]

Pipeline controller notification

No second-stage tests were triggered for this PR.

This can happen when:

• The changed files don't match any pipeline_run_if_changed patterns
• All files match pipeline_skip_if_only_changed patterns
• No pipeline-controlled jobs are defined for the master branch

Use /test ? to see all available tests.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven

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:

• OWNERS [everettraven]

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

[everettraven]

@RadekManak Looks like there are some verify failures. Try a make update followed by a make verify locally to make sure all the generated changes are applied.

Give me a ping when that is done and I'll re-lgtm.