Skip to content

[AFS] Add e2e baseline test for Admission Fair Sharing #5338

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

Open
3 tasks
PBundyra opened this issue May 26, 2025 · 1 comment
Open
3 tasks

[AFS] Add e2e baseline test for Admission Fair Sharing #5338

PBundyra opened this issue May 26, 2025 · 1 comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@PBundyra
Copy link
Contributor

What would you like to be added:
Add e2e baseline test for Admission Fair Sharing into the test/e2e/customconfigs. The scenario could look like this:

  • Create 2 LQs pointing to the same CQ
  • Saturate quota with workloads coming from lq-a
  • Create more workloads from lq-a
  • Create a workload from lq-b
  • Finish some of running workloads
  • Observe workload from lq-b is admitted even it was submitted later than workloads from lq-a

Why is this needed:

Completion requirements:

This enhancement requires the following artifacts:

  • Design doc
  • API change
  • Docs update

The artifacts should be linked in subsequent comments.

@PBundyra PBundyra added the kind/feature Categorizes issue or PR as related to a new feature. label May 26, 2025
@mimowo
Copy link
Contributor

mimowo commented May 26, 2025

/remove-kind feature
/kind cleanup

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed kind/feature Categorizes issue or PR as related to a new feature. labels May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Development

No branches or pull requests

3 participants