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

Clarification on supported versions #1130

Open
mamccorm opened this issue Aug 4, 2024 · 4 comments
Open

Clarification on supported versions #1130

mamccorm opened this issue Aug 4, 2024 · 4 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@mamccorm
Copy link

mamccorm commented Aug 4, 2024

Is your feature request related to a problem?/Why is this needed
I'm looking to find an updated support policy, but the information on this page looks to be outdated: https://kubernetes-csi.github.io/docs/external-snapshotter.html. Particularly it does not list v7 or v8, so guessing its due an update.

Describe the solution you'd like in detail
It'd be great if someone could confirm what the current supported versions are, and if we could document that somewhere

Describe alternatives you've considered
I've looked around but haven't found any others sources of info besides whats linked above

Many thanks

@NymanRobin
Copy link

Hey @mamccorm!
Noticed this issue when passing by 😄

However, I have seen that the information you are looking for is available under the github releases for example for v7.0.0. Moreover I agree that the documentation is problematic and it seems many of the other projects are also struggling with maintaining the compatibility matrix.

I think the flow could potentially be automated when a new release is done or this documentation will always lack behind.

@mamccorm
Copy link
Author

Thanks for stopping by and adding some insights :) In this instance i'm hoping to find an authoritative source that confirms which versions of external-snapshotter are being still actively supported at a given time (i.e not end of life, receiving patch releases etc), as opposed to the compatibility matrix.

I'd be happy to make a contribution to a README / doc here if someone could confirm

@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 Nov 8, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants