Skip to content
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

Open
raffaelespazzoli opened this issue Dec 30, 2020 · 6 comments
Open

ability to inject ca_bundles from configmap #81

raffaelespazzoli opened this issue Dec 30, 2020 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@raffaelespazzoli
Copy link
Contributor

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.

@raffaelespazzoli
Copy link
Contributor Author

This Fixes #41 also when closed.

@mathianasj
Copy link
Contributor

Going to review if this was completed as part of or #82

@raffaelespazzoli raffaelespazzoli added the enhancement New feature or request label Sep 29, 2021
@raffaelespazzoli
Copy link
Contributor Author

@mathianasj can we close this?

@mathianasj
Copy link
Contributor

I will take a look today to make sure it is present

@QuingKhaos
Copy link

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.

@davidkarlsen
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants