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

Add Subject Alternate Names for Ingress Certificates #901

Closed
wants to merge 1 commit into from

Conversation

ryan-a-baker
Copy link

@ryan-a-baker ryan-a-baker commented Mar 15, 2021

This will resolve #900. I hacked around on this a bit and got it to work, but I'm sure there are other (better) ways to handle this. Feel free to steer me in a different direction if there is a better one.

I left the existing $ingress.hosts.core value to maintain backwards compatibility. Was tested with and without alternate host names defined.

@reasonerjt
Copy link
Contributor

See my comment in #900, I hope we hold this for a while as I'm not sure this is very common usage.

@sspreitzer
Copy link

sspreitzer commented Aug 4, 2023

It is 2023, why has noone from the project team reviewed this?

@zyyw ?

Copy link

github-actions bot commented Feb 8, 2024

This PR is being marked stale due to a period of inactivty. If this PR is still relevant, please comment or remove the stale label. Otherwise, this PR will close in 30 days.

@github-actions github-actions bot added the Stale label Feb 8, 2024
Copy link

This PR was closed because it has been stalled for 30 days with no activity. If this PR is still relevant, please re-open a new PR against main.

@github-actions github-actions bot closed this Mar 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support a subject alternate name on ingresses
3 participants