-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[datadog] Add optional kube-state-metrics pod #1011
Conversation
Hi @hkaj. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Can I get a review here, team? |
061e254
to
edbc984
Compare
edbc984
to
0c15770
Compare
Great addition @hkaj . Can't wait for that to get merged :) |
@hkaj: I'm somewhat new to Helm so please excuse me if this doesn't make sense. For pods like kube-state-metrics that are likely dependencies for multiple charts, should they be bundled into individual application charts? The alternative is that we have multiple instances of the same pods running across our infrastructure which seems like a waste of resources. Cheers, edit: maybe this would be better off as a separate chart and a requirement? edit 2: looks like there's on open PR for a kube state metrics chart here. |
@roobert you're right, it's better as another chart. We can switch to a requirement as soon as that PR is merged. And I agree, the risk here is that several charts end up shipping kube-state-metrics (some people use prometheus and datadog, and both will have a kube-state-metrics deployment), that's why I made it optional. This way if you already deploy it another way you can leave it out in the datadog deployment (the datadog agent will still find it and report its metrics), |
#662 has been merged. There are some differences between the |
b86fb9c
to
ef7fef7
Compare
ef7fef7
to
bcef080
Compare
thanks for the feedback @mgoodness |
@mgoodness Resolved the conflicts, can I get a quick review before new ones pop up? |
stable/datadog/Chart.yaml
Outdated
@@ -13,3 +13,5 @@ sources: | |||
maintainers: | |||
- name: Greg Taylor | |||
email: gtaylor@gc-taylor.com | |||
- name: Haissam Kaj |
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.
I don't have the bandwidth to review the rest of this, but wanted to give this the 👍 as the current and only maintainer. The situation should improve greatly in having upstream involved!
@k8s-bot ok to test |
thanks a lot @hkaj :) |
thanks guys! |
* upstream/master: (52 commits) [redmine] add ingress (helm#1336) [stable/jenkins] Use imageTag as version in config map (helm#1333) - Bump to latest Minio release (helm#1304) Update k8s-dashboard note when ingress is enabled (helm#1339) Update etcd-operator to latest release (helm#1248) [stable/nginx-ingress] Add hostNetwork option (helm#1250) Update the CONTRIBUTING.md to reflect the new #helm-users and #helm-dev channels (helm#1315) Submit stable Voyager chart (helm#954) [datadog] Add optional kube-state-metrics pod (helm#1011) [stable/prestashop] Release 0.4.10 (helm#1267) [stable/wordpress] Release 0.6.5 (helm#1270) [stable/phabricator] Release 0.4.9 (helm#1281) [stable/drupal] Release 0.6.2 (helm#1268) Bump aws-cluster-autoscaler to latest. (helm#1101) Use memcached modern recommended options instead (helm#1221) Update NOTES.txt (helm#1316) Rename MARIADB_PORT env var to MARIADB_PORT_NUMBER (helm#1210) Rename POSTGRESQL_PORT env var to POSTGRESQL_PORT_NUMBER (helm#1189) Kubernetes Dashboard Chart (helm#808) Add best practices to requirements (helm#1305) ...
* [datadog] Add optional kube-state-metrics pod * use new kube-state-metrics chart as requirement * Bump to 0.6.0 * bump version and use github ids
Optionally deploy kube-state-metrics to get its (awesome!) metrics out of box. It is automatically discovered by the agent running on the same node so no further configuration is required.
This chart is awesome y'all! Thanks for creating it. We will likely list it as the recommended way to install the agent on Kubernetes.