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
@kdorosh There are two bugs in your helm templates that result in bad manifests.
https://github.com/solo-io/gloo/blob/master/install/helm/gloo/templates/7-gateway-proxy-deployment.yaml
This file will not work if there is more than one gateway proxy defined with helm2. I did not try it with helm3.
Here is part of the generated output. Notice that the separator --- is appended to the line name: envoy-config.
---
name: envoy-config
volumes: - configMap: name: external-gateway-proxy-envoy-config name: envoy-config--- apiVersion: apps/v1
You have another instance of the same bug at the end of the gateway proxy config map template:
port_value: 19000 # if (empty $spec.configMap.data) ## allows full custom--- # config_map apiVersion: v1 kind: ConfigMap
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
@kdorosh There are two bugs in your helm templates that result in bad manifests.
https://github.com/solo-io/gloo/blob/master/install/helm/gloo/templates/7-gateway-proxy-deployment.yaml
This file will not work if there is more than one gateway proxy defined with helm2. I did not try it with helm3.
Here is part of the generated output. Notice that the separator
---
is appended to the linename: envoy-config
.You have another instance of the same bug at the end of the gateway proxy config map template:
The text was updated successfully, but these errors were encountered: