Currently, the Paralus can be exposed using an Ingress resource, especially:
ingress-ztka.yaml, which is serving the TLS/SSL traffic
ingress-console.yaml, which is serving the Dashboard
It would be beneficial if there's the chance to specify specific annotations for each object, rather than having a global set.
What problem does this feature solve? Please link any relevant documentation or Issues
I'm using HAProxy Tech Ingress Controller and the first Ingress object requires a special annotation to offload the TLS/SSL traffic to the pod, instead, the Dashboard one doesn't need this.
However, the Helm Chart doesn't allow specifying specific annotations for each object.
(optional) What is your current workaround?
Manually patching the object upon Helm apply, this doesn't scale approaching a GitOps principle which reapplies the missing annotations.
NikolaBoyko
commented
5 months ago
Briefly describe the feature
Currently, the Paralus can be exposed using an Ingress resource, especially:
ingress-ztka.yaml, which is serving the TLS/SSL trafficingress-console.yaml, which is serving the DashboardIt would be beneficial if there's the chance to specify specific annotations for each object, rather than having a global set.
What problem does this feature solve? Please link any relevant documentation or Issues
I'm using HAProxy Tech Ingress Controller and the first Ingress object requires a special annotation to offload the TLS/SSL traffic to the pod, instead, the Dashboard one doesn't need this.
However, the Helm Chart doesn't allow specifying specific annotations for each object.
(optional) What is your current workaround?
Manually patching the object upon Helm apply, this doesn't scale approaching a GitOps principle which reapplies the missing annotations.