Skip to content
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

Merged
merged 14 commits into from
Jan 18, 2024
Merged

Changes to support TProxy #264

merged 14 commits into from
Jan 18, 2024

Conversation

Ganeshrockz
Copy link
Contributor

@Ganeshrockz Ganeshrockz commented Jan 18, 2024

Changes proposed in this PR:

How I've tested this PR:

Manual & CI

How I expect reviewers to test this PR:

Checklist:

  • Tests added
  • CHANGELOG entry added

@Ganeshrockz Ganeshrockz changed the title Ganeshrockz/t proxy Changes to support TProxy Jan 18, 2024
@Ganeshrockz Ganeshrockz marked this pull request as ready for review January 18, 2024 11:27
@Ganeshrockz Ganeshrockz requested a review from tauhid621 January 18, 2024 11:35
@Ganeshrockz Ganeshrockz merged commit 0f432c6 into main Jan 18, 2024
8 of 9 checks passed
@Ganeshrockz Ganeshrockz deleted the ganeshrockz/t-proxy branch January 18, 2024 12:22
@@ -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.
Copy link
Member

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.

Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants