How to upgrade the operator on Openshift?
llomgui opened this issue · 6 comments
Hello,
The documentation is not very clear about the path to update the operator on Openshift.
According to this markdown , we need to apply CRD as a prerequisite.
What is the next step?
On operator page, we can see the latest version available (2.1.0) but it's impossible to upgrade to it.
Current version: 1.5.0
Update channel: alpha
Update approval: Manual (Don't have any button to upgrade to the latest)
Thank you
Hi @llomgui, can you please explain what you mean by impossible to upgrade to it., are their any logs which you can share as it'll help us understand the issue better. Thanks!
Hello @vepatel,
There is no "seemless upgrade" step available on the operator, there is no button to update it.
Is there any way to do it manually? How to update to ClusterServiceVersion v1.5.2 for example?
Thank you
Hi @llomgui operator exists to make sure that you don't have to manually apply manifests, and it manages the NIC instances.
Uninstalling the Operator does NOT uninstall NGINX Ingress Controller. You should be able to install newer versions without affecting NIC(s) just by clicking Install button in RedHat OpenShift UI
@vepatel Thank you, it worked. I deleted the operator then re-installed it.
I had one error about IngressClass being a string instead of an object. Quick fixed adding name attribute.
Do I have to deal with CRD as indicated by the documentation?
Hi @llomgui, our operator is helm based and unfortunately helm does not handle CRDs upgrades automatically so CRDs have to be applied manually as a pre-req.
see https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations
Thank you for you help. 👍