Set Replace Annotation #108
Conversation
Even though we use 'skipRange' for defining from which versions we can update to the version of the CSV, we also need to add the 'replace' field. It should point to the last released version, and ensures that the old version isn't deleted from the index.
Set bundle csv location once
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: razo7 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 |
|
/test ? |
|
@mshitrit: The following commands are available to trigger required jobs:
Use 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. |
|
/test 4.13-openshift-e2e |
|
/test 4.15-openshift-e2e |
|
/lgtm |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
Even though we use 'skipRange' for defining from which versions we can update to the version of the CSV, we also need to add the 'replace' field. It should point to the last released version and ensure that the old version isn't deleted from the index.
https://docs.engineering.redhat.com/display/CFC/Best_Practices#Best_Practices-SkipRange
Similar to medik8s/self-node-remediation#167 and related to ECOPROJECT-1771