kube-state-metrics
kube-state-metrics copied to clipboard
kubernetes
Stabilization of Autosharding
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
### Tasks
- [ ] Gather some sort of sentiment (understandably hard to do) of why the experimental feature might be hard to maintain. Or things that maybe should change before stabilized.
- [ ] Make changes to autosharding ?
- [ ] Remove feature or remove experimental notices.
- [ ] Update documentation.
Additional context
@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?
@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:
- Confirm that this issue is still relevant with
/triage accepted(org members only) - Close this issue with
/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
