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

Document deployment guidance to deploy ADOT Collector behind a public load balancer #2776

Open
pcesara opened this issue Jul 17, 2024 · 1 comment
Labels

Comments

@pcesara
Copy link

pcesara commented Jul 17, 2024

Is your feature request related to a problem? Please describe.
The current deployment strategies documented focus on daemonset or side car deployments.
While this is helpful for some of the use cases I need to cover, I would also like to deploy a collector available for applications outside AWS that cannot have a collector running as a sidecar.

This is also a useful for when operators wish to run a centralised collector.

Describe the solution you'd like

I would like to have concrete guidance to deploy the collector behind a public load balancer, using ECS.
Guidance would ideally include:

  • Setting up the different components required (Service, Load Balancer, Target Group, Security Groups, etc)
  • Setting up the different ports
  • Security concerns (HTTPS, mTLS)

A prepared CloudFormation stack would be great, similar to what was done for the other deployment strategies.

Describe alternatives you've considered
Manual deployment of the different components required.

Additional context
There is one section in one of the documentation pages that addresses this topic, but very briefly:

Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant