-
Notifications
You must be signed in to change notification settings - Fork 345
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
No way to configure Ingress Trait with annotations #1535
Comments
There's currently an easy way to pass labels as:
The Although there's no corresponding Btw, @xytis can you provide some more references about the way the ingress can be configured via annotations, so we may find a better way to configure it, including TLS support. |
In my experience, Ingress objects generally require at least one annotation: Regarding TLS support, it is a part of current standard Ingress API, but I usually use it in conjunction with certificate manager, which requires even more annotation based configuration. Overall, for now it seems that the best way to handle these kinds of scenarios would be to create the ingress object externally and use |
This issue has been automatically marked as stale due to 90 days of inactivity. |
In many kubernetes deployments, machinery is in place that reacts to Ingress object annotations.
What would be the prefered way to implement passing down these annotations to Ingress Trait object?
Extra: Would it be possible to configure TLS on Ingress Trait object?
The text was updated successfully, but these errors were encountered: