-
Notifications
You must be signed in to change notification settings - Fork 277
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
☂️ Release v0.10.0 requirements #3599
Comments
It is going to be a smaller release than before, but we make it to release the TAS rank-based ordering which is awaited by users. Let me know if we you know about some other candidate features that could make it |
@dgrove-oss @tenzen-y Maybe we could consider graduating ConfigurableResourceTransformations to Beta? |
It's relatively low risk (changing the feature gate to enable by default) and doesn't add/change any API. There hasn't been much time to get user feedback, but that's probably ok. |
Does this indicate that we will graduate both ConfigurableResourceTransformations and WorkloadResourceRequestsSummary to beta? |
Yes, I see no blockers for that |
SGTM, let us collect feedbacks by graduating those to beta |
@dgrove-oss feel free to submit a PR for that |
I have updated the nice-to-haves with 3 related KEPs: |
Also, updated the list with TAS-related pending issues. |
I'm ok to slightly postpone the original release target date to try to include the PRs which look almost ready: |
/close |
@mimowo: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
We are targeting the release for the first week of Dev 2024. Since the date is close and 0.9 was not so long ago we may skip release candidate.
Must Haves
Nice To Haves
.status.TopologyAssignment
field #3671The text was updated successfully, but these errors were encountered: