Skip to content

Upgrade kube-state-metrics to v2.18.0#593

Open
ybykov-a9s wants to merge 1 commit into
cloudfoundry:masterfrom
ybykov-a9s:fix/upgrade-kube-state-metrics-v2
Open

Upgrade kube-state-metrics to v2.18.0#593
ybykov-a9s wants to merge 1 commit into
cloudfoundry:masterfrom
ybykov-a9s:fix/upgrade-kube-state-metrics-v2

Conversation

@ybykov-a9s

@ybykov-a9s ybykov-a9s commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Streamlines upgrades of kube-state-metrics.
Also includes some changes made in V2 of kube-state-metrics.

files:
- common/utils.sh
- github.com/kubernetes/kube-state-metrics/**/*
- kube_state_metrics_exporter/kube-state-metrics_2.18.0_Linux_x86_64.tar.gz

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where does this package come from?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This particular package is a renamed copy of https://github.com/kubernetes/kube-state-metrics/releases/download/v2.18.0/kube-state-metrics_Linux_x86_64.tar.gz.

Two latest releases do not contain binaries on github, but they still can be built from source code.
Can I provide more help regarding the topic?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean in an ideal world we introduce a new way here which we can stick to without manually/ locally build the binary and then use it here, otherwise the release might need to built it, as it did before. Created a Github Issue and asked where the binaries are.

@ybykov-a9s ybykov-a9s changed the title Upgrade kube-state-metrics to v2.19.0 Upgrade kube-state-metrics to v2.18.0 Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants