-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Update README.md for kubernetes_cluster_autoscaler #20061
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
base: master
Are you sure you want to change the base?
Conversation
Thanks for this PR! created DOCS-10610 to review |
@@ -54,7 +59,7 @@ kind: Pod | |||
metadata: | |||
name: '<POD_NAME>' | |||
annotations: | |||
ad.datadoghq.com/controller.checks: | | |||
ad.datadoghq.com/<CONTAINER_NAME>.checks: | |
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.
This <CONTAINER_NAME>
has to match the name of the container defined below line 76.
If we keep a container name hard-coded to controller
line 76, it should be fine to keep controller
here as well.
If we want to be able to customize the name of the container, then, we should also put <CONTAINER_NAME>
below, line 76.
The only parameters required for configuring the `kubernetes_cluster_autoscaler` check are: | ||
|
||
* CONTAINER_NAME | ||
Describe the pod belonging to your cluster autoscaler, and find the container name. |
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.
Describe the pod belonging to your cluster autoscaler, and find the container name. | |
Name of the container of the cluster autoscaler controller. |
What does this PR do?
The Kubernetes Cluster Autoscaler does not work out of the box with the configuration listed in the README.md file.
The default container name changes depending on where it is deployed, and
controller
is not a valid container name for all deployments.Abstracted the readme to highlight the fact that you need to specify the container name as part of the annotation instead of using
controller
for the container name.Motivation
In an AWS EKS deployment, the container name is
aws-cluster-autoscaler
and the integration didn't work out of the box with the instructions from the readme.Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged