I conducted some tests over the past few weeks and identified the root cause of the issue preventing Cilium from upgrading through the operator hub in the OCP environment.
The root cause is that we manually install the clusterserviceversion (CSV) file during the OCP bootstrap, and this becomes a blocker for the operator to receive updates from the OCP operator hub.
In my test environment, when I excluded the clusterserviceversion file, the issue was resolved for both OLM Cilium and OLM EE Cilium when installing the OCP. Therefore, I believe we should not include this clusterserviceversion in the new release. If we include the CSV file during the installation, we can also remove the CSV CR to resolve the issue.
I'm unsure whether we need to prevent the generation of this CSV file or exclude it when generating the manifest folder.
I conducted some tests over the past few weeks and identified the root cause of the issue preventing Cilium from upgrading through the operator hub in the OCP environment.
The root cause is that we manually install the clusterserviceversion (CSV) file during the OCP bootstrap, and this becomes a blocker for the operator to receive updates from the OCP operator hub.
In my test environment, when I excluded the clusterserviceversion file, the issue was resolved for both OLM Cilium and OLM EE Cilium when installing the OCP. Therefore, I believe we should not include this clusterserviceversion in the new release. If we include the CSV file during the installation, we can also remove the CSV CR to resolve the issue.
I'm unsure whether we need to prevent the generation of this CSV file or exclude it when generating the manifest folder.
Here is an example clusterserviceversion file I am referring to: Link to the clusterserviceversion file