Normal Description of problem:
The Cluster Image Registry Operator (CIRO) uses hard coded service details for the IBM Cloud COS Service. These should be collected from the IBM Cloud Global Catalog instead, as their value can be dependent on the environment.
Version-Release number of selected component (if applicable):
4.17.0
How reproducible:
100% when using an environment that utilizes different Plan or Target values for IBM Cloud COS
Steps to Reproduce:
1. Attempt to create an IPI cluster using non-default IBM Cloud Global Catalog service (endpoint)
2. Wait for ClusterOperators to deploy, CIRO fails without ability to use non-default IBM Cloud COS service details (those hardcoded in CIRO).
Actual results:
image-registry False True True 13m Available: The deployment does not exist...
E0529 21:25:40.120323 1 controller.go:377] unable to sync: unable to sync storage configuration: unable to create resource instance: No RC deployments for plan standard with target bluemix-global with resp code: 400, requeuing
Expected results:
Successful CIRO deployment
Additional info:
These are the problematic hardcoded values: https://github.com/openshift/cluster-image-registry-operator/blob/f95b26fd738e04631e4f061c094c2907029b7b9f/pkg/storage/ibmcos/ibmcos.go#L270-L272 IBM Cloud is working on a fix. This is dependent on the API changes and installer fixes for overriding the IBM Cloud Global Catalog, via: https://issues.redhat.com/browse/OCPBUGS-34974
- is blocked by
-
OCPBUGS-34974 [IBMCloud] Require additional service endpoint overrides
-
- ASSIGNED
-
