-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ability to inject ca_bundles from configmap #81
Comments
This Fixes #41 also when closed. |
Going to review if this was completed as part of or #82 |
@mathianasj can we close this? |
I will take a look today to make sure it is present |
Need this as well. The The Cluster Network Operator injects certificates across any namespace when an empty ConfigMap is created with the config.openshift.io/inject-trusted-cabundle=true label, but several components like the GitLab Runner Operator expect the ca-bundle within a secret. Injecting the ca from the above configmap into the secret would be required. |
yes, like https://docs.openshift.com/container-platform/4.14/networking/configuring-a-custom-pki.html#certificate-injection-using-operators_configuring-a-custom-pki - just targeting secrets for the storage. |
ca_bundles are public info and there is a trend now make them available in configmaps rather than secrets. Cert-uitls should support injecting ca_bundles from configmaps.
A single configmap to secret injector should suffice as all other injector support secret as source.
The text was updated successfully, but these errors were encountered: