-
Notifications
You must be signed in to change notification settings - Fork 323
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
Register mesh-gateways using the endpoints controller. #1464
Register mesh-gateways using the endpoints controller. #1464
Conversation
6508cc4
to
8ad1b3d
Compare
b212ca0
to
db72e56
Compare
db72e56
to
b8bda6a
Compare
8f626da
to
921e379
Compare
921e379
to
f5f2d98
Compare
f5f2d98
to
e4ce879
Compare
15c63fe
to
a467499
Compare
Add initial support for the basic service mesh running with agentless. * Update connect-inject deployment to talk to consul servers (currently only in-cluster servers are supported; external servers support will come in a later PR) * Update endpoints controller to register and deregister services and health checks in the catalog and stop using agent APIs * Update connect-init command to take the -node-name flag so that it can search for services within a given node using catalog APIs * Add k8s probes to the envoy container * Provide -node-name flag to the consul connect envoy command so that we can generate correct configuration * Selectively disable acceptance tests that don't yet work in this configuration * Disable consul clients by default
- Use consul-dataplane to configure the mesh-gateway proxy and remove envoy container. - Remove instances of client and auto-encrypt from the deployment.
467c857
to
8784c23
Compare
8ebdab2
to
edc466d
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.
Looks good!!! Thank you so much for doing so much hard work to make it super readable!
There is a couple more fixes I think we need (left in-line) but I won't block the approval on that. To fix acceptance tests, I think we need to remove server restarts from tests because consul-dataplane image we're currently using doesn't support server upgrades. That fix is also probably not relevant anymore, so it's ok to remove it permanently.
1b98c7e
to
be6a786
Compare
be6a786
to
c8e54f1
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.
👍🏻
* Register mesh-gateways using the endpoints controller. - Use consul-dataplane to configure the mesh-gateway proxy and remove envoy container. - Remove instances of client and auto-encrypt from the deployment. * Replace ioutil.ReadFile with os.ReadFile
* Register mesh-gateways using the endpoints controller. - Use consul-dataplane to configure the mesh-gateway proxy and remove envoy container. - Remove instances of client and auto-encrypt from the deployment. * Replace ioutil.ReadFile with os.ReadFile
* Register mesh-gateways using the endpoints controller. - Use consul-dataplane to configure the mesh-gateway proxy and remove envoy container. - Remove instances of client and auto-encrypt from the deployment. * Replace ioutil.ReadFile with os.ReadFile
* Register mesh-gateways using the endpoints controller. - Use consul-dataplane to configure the mesh-gateway proxy and remove envoy container. - Remove instances of client and auto-encrypt from the deployment. * Replace ioutil.ReadFile with os.ReadFile
* Register mesh-gateways using the endpoints controller. - Use consul-dataplane to configure the mesh-gateway proxy and remove envoy container. - Remove instances of client and auto-encrypt from the deployment. * Replace ioutil.ReadFile with os.ReadFile
Changes proposed in this PR:
This requires updating the endpoints controller to parse services that are associated with gateway pods and then register those services with Consul as gateway services. Annotations on the gateway pod is used to determine the kind of the gateway as well as any information required to configure the gateway registration.
How I've tested this PR:
How I expect reviewers to test this PR:
This PR is a little complicated so feel free to pull me into a meeting to ask any questions or understand the changes made here.
Checklist: