-
Notifications
You must be signed in to change notification settings - Fork 324
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
Update Helm Chart for running API Gateways in Agentless config and with external servers #1694
Conversation
Hey @t-eckert just heads up, but just for some clarity I think we probably want the following for full compatibility. Checked are the ones that I think are the highest priority. Agent-based
Agentless
The agentless/external setup will not work with our 0.4 release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally LGTM other than adding a test for CONSUL_HTTP_SSL
. If you need any help verifying the configurations, let me know.
f8e1898
to
b5730b3
Compare
d4c0da2
to
66b9de1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last change to add a test and then I'm good on feedback at this point, though you should probably wait for someone from the k8s team to sign off too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor suggested tweaks to the comments for clarity, overall LGTM and feels like we'll have a good backwards compatibility/upgrade path story with this implemented.
Co-authored-by: Andrew Stucki <andrew.stucki@hashicorp.com>
Co-authored-by: Mike Morris <mikemorris@users.noreply.github.com>
Co-authored-by: Mike Morris <mikemorris@users.noreply.github.com>
Co-authored-by: Mike Morris <mikemorris@users.noreply.github.com>
02de95a
to
d914e2a
Compare
Changes proposed in this PR:
externalServers.httpPort
.CONSUL_HTTP_ADDR
to the first external server host whenexternalServers
is enabled.CONSUL_HTTP_ADDR
using Kube DNS when running with local servers.http(s)://
and instead set this using theCONSUL_HTTP_SSL
environment variable.CONSUL_TLS_SERVER_NAME
to support SNI with external servers.consul.address
for the GatewayClassConfig whether using external or local servers.How I've tested this PR:
0.4.0
with Consul-k8s1.0.0-beta5
(Agentful) and local servers0.5.0
with Consul-k8s1.0.0-beta5
(Agentful) and local servers0.4.0
with Consul-k8s1.0.0-beta5
(Agentless) and local servers0.5.0
with Consul-k8s1.0.0-beta5
(Agentless) and local servers0.4.0
with Consul-k8s1.0.0-beta5
(Agentful) and external servers0.5.0
with Consul-k8s1.0.0-beta5
(Agentful) and external servers0.5.0
with Consul-k8s1.0.0-beta5
(Agentless) and external serversAlso verified that "Deployed API Gateways
0.4.0
with Consul-k8s1.0.0-beta5
(Agentless) and external servers" does not work as is expected.How I expect reviewers to test this PR:
Checklist: