Bug OCPBUGS-2227: Re-enable VPA & CRO operators, move to stable bundle dir

[joelsmith]

No description provided.

[openshift-ci]

@joelsmith: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Re-enable VPA & CRO operators, move to stable bundle dir

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/test-infra repository.

[joelsmith]

See these two PRs which move the 4.12 manifests to stable/:

• Fix stable channel current csv openshift/vertical-pod-autoscaler-operator#129
• Switch to stable channel openshift/cluster-resource-override-admission-operator#88

[openshift-bot]

Build #1

Validating 3 file(s)...
Validating images/clusterresourceoverride.yml...
✅ Validated images/clusterresourceoverride.yml
Validating images/clusterresourceoverride-operator.yml...
✅ Validated images/clusterresourceoverride-operator.yml
Validating images/vertical-pod-autoscaler-operator.yml...
✅ Validated images/vertical-pod-autoscaler-operator.yml

[openshift-ci]

@joelsmith: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Bug OCPBUGS-2227: Re-enable VPA & CRO operators, move to stable bundle dir

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/test-infra repository.

[openshift-ci-robot]

@joelsmith: This pull request references Jira Issue OCPBUGS-2227, which is invalid:

• expected Jira Issue OCPBUGS-2227 to depend on a bug targeting a version in 4.13.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

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/test-infra repository.

[openshift-bot]

Build #2

Validating 3 file(s)...
Validating images/clusterresourceoverride.yml...
✅ Validated images/clusterresourceoverride.yml
Validating images/clusterresourceoverride-operator.yml...
✅ Validated images/clusterresourceoverride-operator.yml
Validating images/vertical-pod-autoscaler-operator.yml...
✅ Validated images/vertical-pod-autoscaler-operator.yml

[openshift-bot]

Build #3

Validating 3 file(s)...
Validating images/clusterresourceoverride.yml...
✅ Validated images/clusterresourceoverride.yml
Validating images/clusterresourceoverride-operator.yml...
✅ Validated images/clusterresourceoverride-operator.yml
Validating images/vertical-pod-autoscaler-operator.yml...
✅ Validated images/vertical-pod-autoscaler-operator.yml

[openshift-bot]

Build #4

Validating 3 file(s)...
Validating images/clusterresourceoverride.yml...
✅ Validated images/clusterresourceoverride.yml
Validating images/clusterresourceoverride-operator.yml...
✅ Validated images/clusterresourceoverride-operator.yml
Validating images/vertical-pod-autoscaler-operator.yml...
✅ Validated images/vertical-pod-autoscaler-operator.yml

[thegreyd]

/lgtm

[openshift-ci-robot]

@joelsmith: All pull requests linked via external trackers have merged:

• openshift/vertical-pod-autoscaler-operator#129
• openshift/cluster-resource-override-admission-operator#88
• openshift/ocp-build-data#2051

Jira Issue OCPBUGS-2227 has been moved to the MODIFIED state.

In response to this:

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/test-infra repository.