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

Infoblox-Provider: Allow to reference CAcert in ConfigMap #327

Open
dermorz opened this issue Oct 24, 2023 · 0 comments
Open

Infoblox-Provider: Allow to reference CAcert in ConfigMap #327

dermorz opened this issue Oct 24, 2023 · 0 comments
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age)

Comments

@dermorz
Copy link

dermorz commented Oct 24, 2023

What would you like to be added:
The DNSProvider for Infoblox has the fields sslVerify and caCert to enable TLS verification. Currently caCert is a string field that requires the user to inline a CA-Certfificate(-chain) to use TLS verification, because the content of that string is directly put into the cert-pool.

I would love to be able to put a reference ConfigMap, that holds the needed CA-Certificate(-chain).

For example it could look like:

# Reference to a ConfigMap with CA certificates. All keys will be iterated and the certificates
# from the values will be added the the external-dns-management trust store. Only needed if
# sslVerify = true and use of self-signed/internal certificate  
caCertRef:
  configMap: 'ca-bundle'

Why is this needed:
For users of trust-manager such ConfigMap is already available for usage and not having to inline the certificate is decreasing the maintainance effort.

@dermorz dermorz added the kind/enhancement Enhancement, improvement, extension label Oct 24, 2023
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age)
Projects
None yet
Development

No branches or pull requests

2 participants