-
Notifications
You must be signed in to change notification settings - Fork 30
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
Changes to support TProxy #264
Conversation
* Changes to support TProxy * Add validation * Added readme * Add comment * Add validation tests
* Cross namespace communication tests * Fix tests * Fix image * Add admin partitions tproxy test
@@ -6,6 +6,18 @@ BREAKING CHANGES | |||
- Adds a new container named `consul-ecs-health-sync` to the task definition which will be responsible for syncing back ECS container health checks into Consul. This container will wait for a successful exit of `consul-ecs-mesh-init` container before starting. | |||
|
|||
FEATURES | |||
* Add support for transparent proxy in ECS tasks based on EC2 launch types. Following are the changes made to the `mesh-task` submodule [[GH-264](https://github.com/hashicorp/terraform-aws-consul-ecs/pull/264)] | |||
- Adds the following variables [[GH-209](https://github.com/hashicorp/terraform-aws-consul-ecs/pull/209)] | |||
- `enable_transparent_proxy` - Defaults to `true`. Fargate based tasks should explicitly pass `false` to avoid validation errors during terraform planning phase. |
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.
@Ganeshrockz should this be a breaking change? Since it will change all the routing, e.g. everything will be routed to/from the proxy.
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.
That makes sense. Will move this under the Breaking changes heading in the next PR
Changes proposed in this PR:
How I've tested this PR:
Manual & CI
How I expect reviewers to test this PR:
Checklist: