Skip to content

Conversation

@felixb-denic
Copy link

Hey,

the current options one has regarding ingress and egress for Grafana in the helm chart is not really flexible, and didn't fit our needs. In the current state of the chart, when providing multiple ports and targets, everything gets rendered into a single rule which is more open than you need.

We wanted something like #3287 but for the egress rules. The problem was that as soon as you set egress.enabled, a rule gets rendered which given the default values, opens up all ports.

I tried to find a way to give the chart more flexibility but without breaking the chart for everyone else. With the new manuelEgress option, the user gets maximum flexibility if needed, but only if the new key is set.

Something like that would probably also be great on the ingress side, but here it's even harder to implement, given the structure of the template and the values, without breaking the chart and requiring a major version bump. But if you are open for a rework of this part of the chart, I'm happy to help.

Best,
Felix

@CLAassistant
Copy link

CLAassistant commented Sep 24, 2025

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants