Assigned
Status Update
Comments
jo...@springer.com <jo...@springer.com> #2
Indeed, this would be quite useful - especially when we need to export the certificates to external systems like an NGINX box.
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com>
me...@google.com <me...@google.com> #3
This would be useful when one wishes to have a Google managed certificate to load into Istio Ingress.
I'm assuming if this feature is implemented, we will get access to download the private key for any Google managed certificate that was generated with the:
gcloud compute ssl-certificates create
command as well.
I'm assuming if this feature is implemented, we will get access to download the private key for any Google managed certificate that was generated with the:
gcloud compute ssl-certificates create
command as well.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
The feature to add Custom Headers exists and can be used with the assitance of a BackendConfig [1]. Currently it's only available for External Ingresses and will not work for Internal ones.
[1]
What you expected to happen:
Customer needs this to be available for Internal ones.
Steps to reproduce:
NA
Other information (workarounds you have tried, documentation consulted, etc):