Bug 1788235
| Summary: | Image Registry CA is not in openshift-config-managed | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Adam Kaplan <adam.kaplan> |
| Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> |
| Status: | CLOSED DEFERRED | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4 | CC: | aos-bugs, bparees |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-07 02:23:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Adam Kaplan
2020-01-06 19:10:29 UTC
The complaint in https://github.com/openshift/cluster-openshift-apiserver-operator/pull/287 appears to be that this code: https://github.com/openshift/cluster-openshift-apiserver-operator/blob/bf1bd305652aa5b9d086b8f782a4508786904a84/pkg/operator/workloadcontroller/workload_controller_openshiftapiserver_v311_00.go#L236-L238 is pulling content from the openshift-image-registry namespace (the content it is pulling is the CA for the internal registry, plus additional external registry CAs that were configured to be trusted via the image-config resource). The complaint appears to be that the apiserver should not read from that namespace directly, the registry should publish the CA it is using to openshift-config-managed, and components that need to talk to it should consume the value from there. So the changes would be: 1) registry publishes its CA to openshift-config-managed (note that actually its CA is the service-signing CA, but it needs to be associated explicitly w/ the internal registry service name, which is what the configmap in question does today) 2) apiserver watches/consumes that configmap, and also needs to watch/consume the image-config resource and it's associated CM to pick up the additional registry CAs that it provides This seems like a pretty minor tech debt issue(and relatively complicated addition to the apiserver operator logic) and as such i'm lowering the severity. Moving to https://issues.redhat.com/browse/DEVEXP-545 to address as tech debt. |