OCPBUGS-64601: Remove SVM console instance if v1alpha1 ConsolePlugin version in present in the CRDs status

[jhadvig]

If the console-plugin-storage-version-migration SVM succeeds we need to remove the ConsolePlugin CRD's status.storedVersions v1alpha1 entry and leave just v1 version.
Implemented retry in case the SVM status condition is not successful, which eventually will leave in SVM deletion, which will kick off its recreation by CVO.

RBAC: Adding patch permissions for the consoleplugins.console.openshift.io CRD.

/assign @TheRealJon @Leo6Leo

@yapei FYI

4.20 backport for testing purposes - #1060

[openshift-ci-robot]

@jhadvig: This pull request references Jira Issue OCPBUGS-52556, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.20.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

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.

In response to this:

If the console-plugin-storage-version-migration SVM succeeds we need to remove the ConsolePlugin CRD's status.storedVersions v1alpha1 entry and leave just v1 version.
Implemented retry in case the SVM status condition is not successful, which eventually will leave in SVM deletion, which will kick off its recreation by CVO.

RBAC: Adding patch permissions for the consoleplugins.console.openshift.io CRD.

/assign @TheRealJon @Leo6Leo

@yapei FYI

4.20 backport for testing purposes - #1060

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.

[TheRealJon]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, TheRealJon

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [TheRealJon,jhadvig]

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

[yapei]

==== initial 419
$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.19.17   True        False         28m     Cluster version is 4.19.17

$ oc edit crd consoleplugins.console.openshift.io --subresource status
customresourcedefinition.apiextensions.k8s.io/consoleplugins.console.openshift.io edited


$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
  "v1",
  "v1alpha1"
]

==== upgraded to 420
$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.1    True        False         125m    Cluster version is 4.20.1

$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
  "v1",
  "v1alpha1"
]

==== upgraded to 421
$ 
$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2025-10-30-013259-test-ci-ln-i9t67s2-latest   True        False         121m    Cluster version is 4.21.0-0-2025-10-30-013259-test-ci-ln-i9t67s2-latest
$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
  "v1"
]

/verified by @yapei

[openshift-ci-robot]

@yapei: This PR has been marked as verified by @yapei.

In response to this:

==== initial 419
$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.19.17   True        False         28m     Cluster version is 4.19.17

$ oc edit crd consoleplugins.console.openshift.io --subresource status
customresourcedefinition.apiextensions.k8s.io/consoleplugins.console.openshift.io edited


$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
 "v1",
 "v1alpha1"
]

==== upgraded to 420
$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.1    True        False         125m    Cluster version is 4.20.1

$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
 "v1",
 "v1alpha1"
]

==== upgraded to 421
$ 
$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2025-10-30-013259-test-ci-ln-i9t67s2-latest   True        False         121m    Cluster version is 4.21.0-0-2025-10-30-013259-test-ci-ln-i9t67s2-latest
$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
 "v1"
]

/verified by @yapei

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.

[yapei]

/retest-required

[jhadvig]

/retest

[jhadvig]

Overriding flaking tests
/override ci/prow/e2e-aws-console

[openshift-ci]

@jhadvig: Overrode contexts on behalf of jhadvig: ci/prow/e2e-aws-console

In response to this:

Overriding flaking tests
/override ci/prow/e2e-aws-console

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]

@jhadvig: all tests passed!

Full PR test history. Your PR dashboard.

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-robot]

@jhadvig: This pull request references Jira Issue OCPBUGS-64601, which is invalid:

• expected the bug to target the "4.21.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.

In response to this:

If the console-plugin-storage-version-migration SVM succeeds we need to remove the ConsolePlugin CRD's status.storedVersions v1alpha1 entry and leave just v1 version.
Implemented retry in case the SVM status condition is not successful, which eventually will leave in SVM deletion, which will kick off its recreation by CVO.

RBAC: Adding patch permissions for the consoleplugins.console.openshift.io CRD.

/assign @TheRealJon @Leo6Leo

@yapei FYI

4.20 backport for testing purposes - #1060

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.

[jhadvig]

/jira refresh

[openshift-ci-robot]

@jhadvig: This pull request references Jira Issue OCPBUGS-64601, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

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

Requesting review from QA contact:
/cc @yapei

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-robot]

@jhadvig: Jira Issue Verification Checks: Jira Issue OCPBUGS-64601
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-64601 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

If the console-plugin-storage-version-migration SVM succeeds we need to remove the ConsolePlugin CRD's status.storedVersions v1alpha1 entry and leave just v1 version.
Implemented retry in case the SVM status condition is not successful, which eventually will leave in SVM deletion, which will kick off its recreation by CVO.

RBAC: Adding patch permissions for the consoleplugins.console.openshift.io CRD.

/assign @TheRealJon @Leo6Leo

@yapei FYI

4.20 backport for testing purposes - #1060

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]

@jhadvig: Jira Issue OCPBUGS-64601 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

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.