Release Beta API version

[dtzar]

User Story

Move from alpha to beta API version, working towards GA stability with the addon provider.

/kind feature

Tasks

Preview Give feedback

1. Make targets should error if REGISTRY is unset #186
   kind/bug lifecycle/rotten triage/accepted +3
   
2. Unable to change namespace #197
   kind/bug +1
   
3. Helm status doesn't update when underlying cluster status changes #196
   kind/bug +1
4. CAAPH report log context "default-context" does not exist while preparing to patch HelmReleaseProxy #199
   kind/bug lifecycle/rotten +2
5. Support one-shot mode #65
   kind/feature +1

[Jont828]

Did you have any criteria in mind for a beta API version? I know we talked about implementing e2e tests for a beta release tag but not the API version

[dtzar]

I like the thinking in this proposal of having just "experimental" and "stable" channels where beta would be a part of the GA channel.
https://docs.google.com/document/d/1uZEhliv1SoQQIi2c6Wmz_n5wYMjwE9Eyr5-mW7OFDYU/edit?usp=sharing

We would merge the existing beta and GA graduation criteria into a single unified set of requirements:

• Full conformance test coverage.
• Multiple conformant implementations.
• Widespread implementation and usage.
• At least 6 months of soak time as an alpha API.
• No significant changes for at least 1 minor release and 3 months
• Approval from subproject owners + KEP reviewers.

[Jont828]

I think that makes sense. So under that proposal, would we cut a stable release soon and keep a series of alpha/exp releases that run ahead of it?

[k8s-triage-robot]

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

[dtzar]

/remove-lifecycle stale

[dtzar]

I believe the task list just created now is the criteria for a beta release.
There is no ETA on a beta timeline. Contributions welcome!

We would like to have releases ~ every 2 months (even if just dep updates).

[k8s-triage-robot]

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-triage-robot]

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