Details
-
Task
-
Resolution: Done
-
Major
-
1.8.0.GA
-
None
-
False
-
False
Description
Currently KC CR does not allow for any configuration of generated BuildConfig. This is problematic if kafka base image is hosted on authenticated registry other than registry.redhat.io
- customers might want to use this approach for disconnected installs (although the registry might not be authenticated in such case, we should not assume that will be the case. This something which would be up to customer's internal policies)
- QE often transfers images from brew to private registries under rh_integration organisation on quay in order to access them from OCP clusters running outside of RH's internal network.
The obvious workaround of setting the pull secret directly on generated BuildConfig fails due to reconciliation removing such modifications.
The desired strategy part of BC should look like this
strategy: type: Docker dockerStrategy: pullSecret: name: my-secret