Description
Type of question
Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
Question
What did you do?
I have a operator installed with version v1 and have config the manually approve method for the operator.
When I have a new catalogsource image promoted which triggered the catalogsource updated, it will generated a new Install plan to request to apply the update.
When I select approve, it will install the new version of operators. that's fine
But When I want to deny the install plan request, seems I can not only deny the upgrade request, the deny operators will also remove my existing operators as well. that's not make sense for me.
What did you expect to see?
I just want to deny the upgrade installplan without clean up my existing operators.
What did you see instead? Under which circumstances?
The current behavior is, when I select deny, it will remove my existing operators as well. I need to reinstall it.
Environment
- operator-lifecycle-manager version:
hchenxa@hchenxadembp:common-svcs-sert-tests$ oc get co | grep operator-lifecycle-manager
operator-lifecycle-manager 4.5.0 True False False 101m
- Kubernetes version information:
- Kubernetes cluster kind:
Additional context
Add any other context about the question here.