search

kubernetes / cloud-provider-vsphere

Kubernetes Cloud Provider for vSphere https://cloud-provider-vsphere.sigs.k8s.io
Apache License 2.0
244 stars 177 forks source link

Document a support policy/commitment for Kubernetes versions #465

Closed ibauersachs closed 8 months ago

ibauersachs commented 3 years ago

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened: The documentation does not provide a support policy for new Kubernetes releases. E.g. v1.19.0 of cloud-provider-vsphere was released on Jan 14 2021, while Kubernetes v1.19 was released on 26 August 2020. Similarly, there is no stable release of cloud-provider-vsphere v1.20 yet (with Kubernetes released 8 December 2020, more than 5 months ago), and Kubernetes is already at v1.21 (released over a month ago).

What you expected to happen: Document the level of guaranteed support, i.e. that there will be a matching stable cloud-provider-vsphere release within N weeks of a Kubernetes release.

I realize this is an open-source project, but since this provider is only usable in a commercial, paid-for product (vSphere), and most of the recent commits are from VMware employees, IMO it's not too much to ask. If it is not possible to provide such a guarantee and the project is only maintained on a best-effort basis, this should also be documented.

Anything else we need to know?: Related to #457.

Environment: n/a

nicolehanjing commented 3 years ago

@ibauersachs We added the release matrix to README file last week: https://github.com/kubernetes/cloud-provider-vsphere/pull/459, hope that helps :)

ibauersachs commented 3 years ago

@nicolehanjing The information merged in #459 doesn't answer my question at all. It doesn't contain any timeline for new versions nor a support promise.

nicolehanjing commented 3 years ago

I think our current policy is that when a new Kubernetes release comes out, we will bump our k8s dependencies and cut a new release for cloud provider vsphere. e.g. v1.19.x of cloud-provider-vsphere was released after k8s v1.19 comes out sometimes we delay our release because of testing for new features or bug fixes

k8s-triage-robot commented 3 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

ibauersachs commented 3 years ago

An official documentation for supported versions and a support policy (like in the CSI documentation) is still missing.

/remove-lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

mohag commented 2 years ago

/remove-lifecycle rotten

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

mohag commented 1 year ago

/remove-lifecycle rotten

This probably needs some occasional +1 posts (since there is a bot)

Currently Kubernetes 1.26 is out and the latest version of this is 1.24...

Edit: Actually 1.25 seems to be out, far down the releases list...

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle stale

liggitt commented 1 year ago

/remove-lifecycle stale

this is still relevant... Kubernetes 1.27 is out and the latest supported version here is indicated to be 1.26

is there a tracking issue or documented timeline for new minor versions to be supported here?

chenguo-github commented 1 year ago

+1 for the same question. Is there any plan / timeline to support new minor versions? Thanks!

k8s-triage-robot commented 10 months ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 9 months ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 8 months ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 8 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/cloud-provider-vsphere/issues/465#issuecomment-2011184406): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.