Skip to content

Conversation

@mpatlasov
Copy link
Contributor

@mpatlasov mpatlasov commented Oct 20, 2025

New annotation release.openshift.io/desired-version will be used by CSO to compare the version from env var OPERATOR_IMAGE_VERSION with actual version of currently running operand.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 20, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 20, 2025

@mpatlasov: This pull request references STOR-2523 which is a valid jira issue.

Details

In response to this:

New annotation release.openshift.io/desired-version will be used by CSO to compare the version from env var OPERAND_IMAGE_VERSION with actual version of currently running operand.

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 openshift-ci bot requested review from jsafrane and mandre October 20, 2025 05:05
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpatlasov

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 Oct 20, 2025
@mpatlasov
Copy link
Contributor Author

/retest-required

1 similar comment
@mpatlasov
Copy link
Contributor Author

/retest-required

@mpatlasov
Copy link
Contributor Author

/assign @jsafrane

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 27, 2025

@mpatlasov: This pull request references STOR-2523 which is a valid jira issue.

Details

In response to this:

New annotation release.openshift.io/desired-version will be used by CSO to compare the version from env var OPERATOR_IMAGE_VERSION with actual version of currently running operand.

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.

@mpatlasov mpatlasov force-pushed the STOR-2523-Add-desired-version-annotation branch from 0a05ff2 to c8afe69 Compare October 27, 2025 07:07
@mpatlasov mpatlasov force-pushed the STOR-2523-Add-desired-version-annotation branch from c8afe69 to 15fdfe0 Compare December 3, 2025 03:08
@mpatlasov
Copy link
Contributor Author

@jsafrane , the PR is ready for review (last commit implements DeploymentVersionController). PTAL

@mpatlasov mpatlasov force-pushed the STOR-2523-Add-desired-version-annotation branch from 15fdfe0 to 64cf8b0 Compare December 3, 2025 23:45
@mpatlasov
Copy link
Contributor Author

/retest-required

@mpatlasov
Copy link
Contributor Author

/hold
(until 4.21 branches)

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 5, 2025
@mpatlasov mpatlasov changed the title STOR-2523: hypershift: Add desired-version annotation to operand Deployments STOR-2523: hypershift: Add desired-version annotation to operand Deployments and use DeploymentVersionController in CSO Dec 5, 2025
New annotation `release.openshift.io/desired-version` will be used by CSO to compare the version from env var `OPERATOR_IMAGE_VERSION` with actual version of currently running operand.
`go get github.com/openshift/library-go`
New annotation `release.openshift.io/version` signals that rollout of Deployment is complete (see https://issues.redhat.com/browse/STOR-2523 for details).
This commit uses new controller (DeploymentVersionController) from library-go which reconciles version annotation if controller deplyment is done.
@mpatlasov mpatlasov force-pushed the STOR-2523-Add-desired-version-annotation branch from 64cf8b0 to 1a3bf7c Compare January 8, 2026 02:47
@mpatlasov
Copy link
Contributor Author

Update: last force-push only rebased PR on top of current head of main branch.

@mpatlasov
Copy link
Contributor Author

/unhold
(4.21 branched, we can proceed with merging this PR for 4.22)

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 8, 2026
@mpatlasov
Copy link
Contributor Author

/override ci/prow/okd-scos-images
OKD has a known outage

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

@mpatlasov: Overrode contexts on behalf of mpatlasov: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images
OKD has a known outage

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

@mpatlasov: 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

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.

3 participants