-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Add client TLS flags for AWS provider #5026
Comments
Hi @cavdhut Sure go ahead. /help |
@ivankatliarchuk: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/help |
@cavdhut are you working on this? If not I can take it up |
@hjoshi123 Please take it. I did not get chance to look into this. |
/assign |
We utilize the AWS provider with external DNS running behind a forward proxy, which requires presenting client TLS certificates during requests. According to the documentation at https://github.com/kubernetes-sigs/external-dns/blob/master/docs/flags.md, it appears that specifying TLS client certificates and keys via --tls-client-cert and --tls-client-cert-key input arguments is supported. However, upon further investigation of the code, it seems that the AWS provider does not currently support this.
We would like to request the addition of this support for the AWS provider. If this is acceptable, I can look into creating a pull request (PR) to implement this feature.
The text was updated successfully, but these errors were encountered: