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
Support a subject alternate name on ingresses #900
Comments
@ryan-a-baker |
I understand. This was something I did a while back and just now opening the PR for it. We can work around it for now. In the meantime, I'll add more testing results and context to the issue and the PR, as I did this all in a bit of a hurry. |
I'd like to add a plus one to this -- we also have a globally replicated harbor deployment |
Adding my 👍 to this request. Seems trivial. |
We are facing the same limitation. We have a new harbor deployment with a new hostname, but we have to be backward-compatible with the old hostname. The plan is that the old hostname becomes a CNAME for the new one. I have modified the ingress resource, so that
|
Hi everyone We are facing the same limitation here. Supporting multiple hosts for the core ingress seems like good practice. Adding my 👍 here. |
Adding my 👍 to this request as well. |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue. |
We have a globally replicated Harbor instance, and I'd love to front it all with DNS leveraging Geo-location.
Unfortunately, I'm unable to do this because the value for the ingress host is only a single entry. The helm chart should support multiple hosts so that dynamically generated certificates (such as Let's Encrypt) can have SANs.
The text was updated successfully, but these errors were encountered: