-
Notifications
You must be signed in to change notification settings - Fork 474
AWS Fargate: Add disclaimer that integration supports ECS only #10613
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
Conversation
|
💚 Build Succeeded
History
cc @zmoog |
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.
LGTM!
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.
LGTM
Package awsfargate - 1.2.1 containing this change is available at https://epr.elastic.co/search?package=awsfargate |
…ic#10613) * Add disclaimer that integration supports ECS only
…ic#10613) * Add disclaimer that integration supports ECS only
Proposed commit message
Clarify the AWS Fargate integration documentation, saying that this integration supports Amazon ECS clusters only. Unfortunately, today, it does not support EKS clusters managing nodes with a Fargate profile.
More than one user contacted the support team, asking why the AWS Fargate doesn't work on the EKS cluster. The docs state that it works with ECS clusters only, but more is needed.
Checklist
I have verified that all data streams collect metrics or logs.changelog.yml
file.I have verified that Kibana version constraints are current according to guidelines.