Open hdost opened 1 year ago
@hdost likely it can be considered stable since there were no drastic changes (if at all) in the last releases to it. What would help promoting it to stable is user feedback like yours. Are you using it in production? Is it working as expected? Are there any outstanding issues?
/assign @CatherineF-dev /triage accepted
@hdost likely it can be considered stable since there were no drastic changes (if at all) in the last releases to it.
What would help promoting it to stable is user feedback like yours. Are you using it in production? Is it working as expected? Are there any outstanding issues?
Currently we are not but we are considering it. However it was a point of hesitation to design some changes only to have the feature be removed. At least we can start to test it out. For sure some feedback to come as we test. 👍🏼
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted
(org members only)/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
@CatherineF-dev any updates on this issue?
/triage accepted
What would you like to be added:
Autosharding stabilized and not considered experimental.
Why is this needed:
The experimental feature has been experimental for 5 years. It's not clear to me (and likely other users) what the actual status of this is. Introduced in 1.8.0 now on 2.7.0 at time of writing this. Is it still experimental? What would prevent it from becoming stable? What should be done before it becomes stable?
Describe the solution you'd like
Nothing new necessarily, but mostly
Additional context