Move equivalence class based scheduling to beta

[misterikkit]

Feature Description

• One-line feature description (can be used as a release note): Cache scheduling decisions of equivalent pods
• Primary contact (assignee): @resouer, @misterikkit
• Responsible SIGs: @kubernetes/sig-scheduling-feature-requests
• Design proposal link (community repo): Equivalence class based scheduling in Kubernetes
• Link to e2e and/or unit tests: test/e2e/scheduling/equivalence_cache_predicates.go
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @davidopp, @bsalamat , @erictune, @k82cn, @timothysc, @wojtek-t
• Approver (likely from SIG/area to which feature belongs): @davidopp, @wojtek-t
• Feature target (which target equals to which milestone):
  • Alpha already released: 1.8
  • Beta release target: 1.11
  • Stable release target: 1.12

This feature was already implemented by @resouer and is currently in alpha. There is some remaining work to get the feature ready for beta & ga.

Original issue:

• Implement "equivalence classes" and caching thereof kubernetes#17390

Remaining issues (will be periodically updated):

• Full integration test is required: Add scheduler integration test for volume predicate equivalence cache invalidation kubernetes#56104
• Amend and enable e2e test: Add pvc as part of equivalence hash kubernetes#56577 (comment)
• Fix potential data race: TODO
• Evaluate and fix potential improvements:
  • speed up invalidate operation (or not)TODO
  • minimize invalidation scope, TODO-1 TODO-2
• Compute pod equivalence based on pod properties and not OwnerReference.

/sig scheduling

[k8s-ci-robot]

@misterikkit: Reiterating the mentions to trigger a notification:
@kubernetes/sig-scheduling-feature-requests

In response to this:

Feature Description

• One-line feature description (can be used as a release note): Cache scheduling decisions of equivalent pods
• Primary contact (assignee): @resouer, @misterikkit
• Responsible SIGs: @kubernetes/sig-scheduling-feature-requests
• Design proposal link (community repo): Equivalence class based scheduling in Kubernetes
• Link to e2e and/or unit tests: test/e2e/scheduling/equivalence_cache_predicates.go
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @davidopp, @bsalamat , @erictune, @k82cn, @timothysc, @wojtek-t
• Approver (likely from SIG/area to which feature belongs): @davidopp, @wojtek-t
• Feature target (which target equals to which milestone):
• Alpha already released: 1.8
• Beta release target: 1.11
• Stable release target: 1.12

This feature was already implemented by @resouer and is currently in alpha. There is some remaining work to get the feature ready for beta & ga.

Original issue:

• Implement "equivalence classes" and caching thereof kubernetes#17390

Remaining issues (will be periodically updated):

• Full integration test is required: Add scheduler integration test for volume predicate equivalence cache invalidation kubernetes#56104
• Amend and enable e2e test: Add pvc as part of equivalence hash kubernetes#56577 (comment)
• Fix potential data race: TODO
• Evaluate and fix potential improvements:
  • speed up invalidate operation (or not)TODO
  • minimize invalidation scope, TODO-1 TODO-2
• Compute pod equivalence based on pod properties and not OwnerReference.

/sig scheduling

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/test-infra repository.

[timothysc]

This is not a user-facing feature, so there is no need to promote a high-level feature imo. It's internal refactorings that ideally should have no user-facing changes.

[misterikkit]

I guess that explains why I could not find any release notes for the alpha feature. We need a place to discuss and track remaining work items. Do you think this should just be an issue in kubernetes/kubernetes?

[bsalamat]

I agree with @timothysc, but this feature has not been enabled by default (as it is an alpha feature). We should bring it to production quality and enable it by default. I guess that's what we mean by moving this to beta.

[misterikkit]

This feature has moved to kubernetes/kubernetes#58222