We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is an amazing plugin. Incredibly useful.
I think the template substitution may cause grief in the helm chart when specifying multiple domains.
domain: mydomain.com
works fine
domain: mydomain.com myseconddomain.com
causes both to fail.
I believe it is because the configmap is generated like so
k8s_gateway "mydomain.com" { apex k8s-gateway.infra-system ttl 300 }
and
k8s_gateway "mydomain.com myseconddomain.com" { apex k8s-gateway.infra-system ttl 300 }
Workaround: editing the configmap in the second case to not have quotes. E.g.
k8s_gateway mydomain.com myseconddomain.com { apex k8s-gateway.infra-system ttl 300 }
works perfectly, but does mean it needs to be edited by hand after the helm deploy :).
Note: I'm deploying this using argocd, so unsure if that is maybe interfering as well. I would think not, but worth mentioning.
The text was updated successfully, but these errors were encountered:
could be it just a matter of removing " in this line?
"
k8s_gateway/charts/k8s-gateway/templates/configmap.yaml
Line 23 in aaa1863
@btrepp do you want to test to see if it works?
Sorry, something went wrong.
Bit of a noob on this but will do when I get a chance :)
Hello, I have the same need, so this "simple" evolution could really be cool :)
No branches or pull requests
This is an amazing plugin. Incredibly useful.
I think the template substitution may cause grief in the helm chart when specifying multiple domains.
works fine
causes both to fail.
I believe it is because the configmap is generated like so
and
Workaround:
editing the configmap in the second case to not have quotes. E.g.
works perfectly, but does mean it needs to be edited by hand after the helm deploy :).
Note: I'm deploying this using argocd, so unsure if that is maybe interfering as well. I would think not, but worth mentioning.
The text was updated successfully, but these errors were encountered: