Skip to content

OCPSTRAT-1751: Control plane version status enhancement#1950

Open
enxebre wants to merge 3 commits intoopenshift:masterfrom
enxebre:controlplane-version-report
Open

OCPSTRAT-1751: Control plane version status enhancement#1950
enxebre wants to merge 3 commits intoopenshift:masterfrom
enxebre:controlplane-version-report

Conversation

@enxebre
Copy link
Member

@enxebre enxebre commented Feb 27, 2026

Summary

  • Add controlPlaneVersion field to HostedClusterStatus and HostedControlPlaneStatus
  • Tracks management-side control plane component version history independently from CVO-reported version
  • Uses a dedicated ControlPlaneVersionStatus type with desired, history, and observedGeneration fields
  • Enables service providers (ROSA/ARO) to detect completed control plane upgrades, verify CVE patches, and compute NodePool version skew without waiting for data-plane rollout

Test plan

  • Unit tests for reconciliation logic
  • E2E tests for z-stream and y-stream upgrade history
  • Validation with zero-NodePool clusters

🤖 Generated with Claude Code

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 27, 2026

@enxebre: This pull request references OCPSTRAT-1751 which is a valid jira issue.

Details

In response to this:

Summary

  • Add controlPlaneVersion field to HostedClusterStatus and HostedControlPlaneStatus
  • Tracks management-side control plane component version history independently from CVO-reported version
  • Uses a dedicated ControlPlaneVersionStatus type with desired, history, and observedGeneration fields
  • Enables service providers (ROSA/ARO) to detect completed control plane upgrades, verify CVE patches, and compute NodePool version skew without waiting for data-plane rollout

Test plan

  • Unit tests for reconciliation logic
  • E2E tests for z-stream and y-stream upgrade history
  • Validation with zero-NodePool clusters

🤖 Generated with Claude Code

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 27, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 27, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign enxebre for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

Address review feedback:
- Use dedicated ControlPlaneVersionStatus type instead of reusing
  ClusterVersionStatus (omits unused AvailableUpdates and
  ConditionalUpdates fields)
- Add CPO glossary entry
- Move ControlPlaneUpToDate condition discussion to Alternatives
- Reword OVN limitation, summary, and motivation sections
- Remove line breaks, use full line length

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@enxebre enxebre force-pushed the controlplane-version-report branch 7 times, most recently from 76d296d to c46e84a Compare February 27, 2026 11:51
@enxebre enxebre force-pushed the controlplane-version-report branch from c46e84a to 33a856b Compare February 27, 2026 16:04
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@enxebre enxebre force-pushed the controlplane-version-report branch from 33a856b to c667f69 Compare February 27, 2026 16:36
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 27, 2026

@enxebre: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants