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

Is GCP Compute Persistent Disk CSI Driver v1.13.x compatible with k8s v1.30 and v1.31? #1828

Open
mooneeb opened this issue Sep 18, 2024 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@mooneeb
Copy link

mooneeb commented Sep 18, 2024

According to the Kubernetes Version Recommendation section in the repo's README, the compatibility matrix for v1.13 points to the HEAD commit of the Kubernetes repo.

This was previously k8s. Since then v1.31 has been introduced so the HEAD is pointing at k8s v1.31.

Does this mean v1.13 is compatible with both v1.30 and v1.31?

v1.30 is missing from the map so I wanted to clear the confusion.

Thank you :)

@mooneeb
Copy link
Author

mooneeb commented Sep 19, 2024

I also see v1.14 and v1.15 have been released but the table is not updated with their compatibility.

As per

The latest stable of this driver is recommended for the latest stable Kubernetes version.

This implies v1.15 of GCP Compute Persistent Disk CSI Driver show now be compatible with the HEAD commit (i.e. k8s v1.31).

If so then what are the recommended versions for v1.13 and v1.14.

Would appreciate some guidance here :)

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants