Skip to content
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

What is kube-state-metrics status on Kubernetes 1.29? #2323

Closed
benoit74 opened this issue Feb 19, 2024 · 5 comments
Closed

What is kube-state-metrics status on Kubernetes 1.29? #2323

benoit74 opened this issue Feb 19, 2024 · 5 comments
Assignees
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@benoit74
Copy link

Kubernetes 1.29 is still not mentioned in https://github.com/kubernetes/kube-state-metrics#compatibility-matrix

Is there any known issues on 1.29? Is there any plan to do a real release supporting 1.28 / 1.29?

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 19, 2024
@dashpole
Copy link

/triage accepted
/assign @CatherineF-dev

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 22, 2024
@CatherineF-dev
Copy link
Contributor

@McDonald755
Copy link

I need him, too. Please release it as soon as possible

@liangyuanpeng
Copy link
Contributor

Working at:

@mrueg
Copy link
Member

mrueg commented Mar 26, 2024

Main branch is now at k8s 1.29 0cb2965

Let us know if there's any urgency behind it. Usually Kubernetes provides great compatibility between multiple a couple of minor releases.

@mrueg mrueg closed this as completed Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants