Open morotsgurka opened 3 days ago
You're right, for simplicity, the template is using only 1 route. If we change this, it would be breaking for everyone.
We’re unsure about the use case and the traction it will receive. We are going to leave the status as kind/proposal to give the community time to let us know if they would like this idea.
We will reevaluate as people respond.
Welcome!
What did you expect to see?
Hi!
I'm using Authentik Proxy Provider for authentication on a k3s cluster. To define the authentication I need 2 Rules in the routes of the IngressRoute. Here is an example of my ingress for Longhorn's WebUI:
From what I've read/understood, the values for the ingressRoute -> Dashboard uses this template file?
It then matches with "matchRule" from the values.yaml?
So my suggestion is having "routes: []" in values.yaml something like this:
And then update the ingressRoute template file to loop through(?) the routes specified. This would/should keep the default deployment the same but allow users to specify more than one match rule.
I'm no helm-chart expert so excuse me if I've simply misunderstood something about how helm charts/values work