New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove managed-velero-operator #171
Conversation
Managed-velero-operator is now deployed using the app-sre pipeline. openshift/managed-velero-operator#20
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dak1n1 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold
@@ -1,6 +0,0 @@ | |||
apiVersion: v1 | |||
kind: Namespace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think deleting this will delete the NS and the Velero CRs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested in hive-stage, and it appears to keep the namespace and CR around when the SelectorSyncSet is deleted.
Managed-velero-operator is now deployed using the app-sre pipeline.
openshift/managed-velero-operator#20