[metricbeat] Follow migration from kube-state-metrics charts out of stable repo

[jmlrt]

Metricbeat chart currently use kube-state-metrics chart as subchart to get metrics from K8S.

As Stable repo will be deprecated in November 2020 (see Deprecation timeline), kube-state-metrics chart will need to migrate to another repository.

This work seem to be tracked in kubernetes/kube-state-metrics#1153.

When the migration will be over, Metricbeat chart will need to be updated to get kube-state-metrics subchart from its new home.

[jmlrt]

While waiting for kube-state-metrics chart migration to a new GitHub repository, We need to update Metricbeat chart requirements to retrieve the subchart from the new stable Helm repos url => #882

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[jmlrt]

For later reference, kube-state-metrics chart is now hosted at https://github.com/kubernetes/kube-state-metrics/tree/master/charts/kube-state-metrics

[christophercutajar]

While deploying an ECK cluster using terraform, I've deployed kube-state-metrics v2.13.0 using the official chart from https://kubernetes.github.io/kube-state-metrics. One breaking change I've encountered in the official helm chart is in below line:

helm-charts/metricbeat/templates/deployment.yaml

Line 121 in 0ff3a3c

value: "$({{ .Release.Name | replace "-" "_" | upper }}_KUBE_STATE_METRICS_SERVICE_HOST):$({{ .Release.Name | replace "-" "_" | upper }}_KUBE_STATE_METRICS_SERVICE_PORT_HTTP)"

As a solution, I've changed the aforementioned line to read as follows: "$(KUBE_STATE_METRICS_SERVICE_HOST):$(KUBE_STATE_METRICS_SERVICE_PORT_HTTP)"

Metricbeat deployment was deployment successfully with this change.

Happy to help in fully testing and performing the necessary changes!

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[christophercutajar]

@jmlrt let me know how can I help in achieving this!

[jmlrt]

Hi @christophercutajar,
Sorry I totally missed your previous comment.
Thanks for your help!

I didn't try the new kube-state-metrics yet. It seems you did it.

Do you think you could create a PR?

Also, the most important things to check is to ensure that metrics are reported correctly with this new version and to check if metricbeat upgrade tests are successful (https://devops-ci.elastic.co/view/Helm%20Charts/job/elastic+helm-charts+pull-request+integration-metricbeat/1067/).

[jmlrt]

For the records, the new chart code is here:

• https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-state-metrics
• https://artifacthub.io/packages/helm/prometheus-community/kube-state-metrics/

[christophercutajar]

We've been using kube-state-metrics v2.13.0 it productions since March - https://github.com/elastic/seceng/issues/2028 and didn't had any issues but we need to perform testing with the latest version.

I'll work on it in the next couple of days and will create the necessary PR.

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[christophercutajar]

Haven't been able to dedicate time to this. Will plan for this during January

[jmlrt]

This was done in #1524.