csv: rename deployment (PROJQUAY-3239) #56
Conversation
|
/cherrypick redhat-3.6 |
|
@ricardomaraschini: once the present PR merges, I will cherry-pick it on top of redhat-3.6 in a new PR and assign it to you. 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: HammerMeetNail, ricardomaraschini 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:
Approvers can indicate their approval by writing |
|
/retest |
On v3.6.3 the selectors have changed. Selectors are, according to OLM, an immutable field therefore we need to rename the deployment. By renaming the deployment OLM will delete the previous deployment and create a new one: operator-framework/operator-lifecycle-manager#952 (comment)
|
@ricardomaraschini: new pull request created: #57 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. |
|
/cherrypick redhat-3.7 |
|
@ricardomaraschini: new pull request created: #58 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. |
On v3.6.3 the selectors have changed. Selectors are, according to OLM,
an immutable field therefore we need to rename the deployment.
By renaming the deployment OLM will delete the previous deployment and
create a new one:
operator-framework/operator-lifecycle-manager#952 (comment)