You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the className setting for Ingress contains magic to add annotations if it equals nginx, public, and traefic. The design is misleading, because one can install e.g. multiple nginx-ingress controllers each one under a different name. One would expect that annotations under .Values.ingress.annotations.nginx will be used for all of them.
Also noticed, that the MQ Ingress is missing base annotations.
The text was updated successfully, but these errors were encountered:
gw0
changed the title
Support different classNames for Ingress
Support different classNames for assigning annotations to Ingresses (or drop the magic)
Jan 24, 2023
Currently, the
className
setting for Ingress contains magic to add annotations if it equalsnginx
,public
, andtraefic
. The design is misleading, because one can install e.g. multiplenginx-ingress
controllers each one under a different name. One would expect that annotations under.Values.ingress.annotations.nginx
will be used for all of them.Also noticed, that the MQ Ingress is missing base annotations.
The text was updated successfully, but these errors were encountered: