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

Support different annotations on an Ingress basis #98

Open
prometherion opened this issue Sep 27, 2023 · 1 comment
Open

Support different annotations on an Ingress basis #98

prometherion opened this issue Sep 27, 2023 · 1 comment
Labels
enhancement New feature or request new Needs triage

Comments

@prometherion
Copy link

Briefly describe the feature

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.

@prometherion prometherion added enhancement New feature or request new Needs triage labels Sep 27, 2023
@NikolaBoyko
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new Needs triage
Projects
None yet
Development

No branches or pull requests

2 participants