Closed Elyytscha closed 2 years ago
We edited this as workaround for now in the csv directly in the openshift-operators namespace and also in the operator deployment to 512Mi, which seems sufficient for now. But we think this manual edit is lost when we upgrade the operator
https://github.com/application-stacks/runtime-component-operator/blob/044b87e47baa346601385e7c69059065ecb77bfe/bundle/manifests/runtime-component.clusterserviceversion.yaml#L440
In our case on openshift this is not enough and our RCO Operator keeps crashing.. So we need to adjust this somehow manually.. also not sure how to do that, thats its persisted when operator upgrades..
We are getting OOMKill, so explicitly memory limits seems to low.