chore: upgrade kube-state-metrics to 2.14.0 #3865
Conversation
Signed-off-by: Eric Chlebek <echlebek@sumologic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
The upgrade looks fine, but have you checked that there are no important or even breaking changes since 2.7? I know it's "only" minor versions, but you'd be surprised how many components use very loose definitions of semver 😅 |
Signed-off-by: Eric Chlebek <echlebek@sumologic.com>
|
@ccressent There are no advertised breaking changes, so hopefully all goes well. There have been many, many bug fixes, if one of them breaks something for someone, we will likely have to work around it. |
Signed-off-by: Eric Chlebek <echlebek@sumologic.com>
|
@ccressent Looks like all did not go well, but it's because our chart is pulling kube-state-metrics out of our own ECR. I have no idea why it's doing that but it seems related to some openshift incompatibility. |
| @@ -1098,7 +1098,7 @@ kube-prometheus-stack: | |||
| ## so we bump the image manually. | |||
| image: | |||
| repository: public.ecr.aws/sumologic/kube-state-metrics | |||
| tag: "v2.7.0" | |||
| tag: "v2.14.0" | |||
There was a problem hiding this comment.
I would try to test with this version on a vagrant box or using kind.
There was a problem hiding this comment.
@rnishtala-sumo I can do that once I get the integration tests passing
Checklist