Skip to content
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

Support Hierarchical Cohorts with FairSharing #3759

Open
3 tasks
mimowo opened this issue Dec 6, 2024 · 3 comments
Open
3 tasks

Support Hierarchical Cohorts with FairSharing #3759

mimowo opened this issue Dec 6, 2024 · 3 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@mimowo
Copy link
Contributor

mimowo commented Dec 6, 2024

What would you like to be added:

Proper support for Hierarchical Cohorts with Fair Sharing. Determine what are the gaps to make it officially supported and implement the support.

Why is this needed:

Currently the behavior for combining Hierarchical Cohorts with FairSharing is undefined. See:

// Cohort is the Schema for the cohorts API. Using Hierarchical
// Cohorts (any Cohort which has a parent) with Fair Sharing
// results in undefined behavior in 0.9

Completion requirements:

This enhancement requires the following artifacts:

  • Design doc
  • Implementation
  • Docs update

The artifacts should be linked in subsequent comments.

@mimowo mimowo added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 6, 2024
@mimowo
Copy link
Contributor Author

mimowo commented Dec 6, 2024

/assign @gabesaba
tentatively
cc @mwielgus @mwysokin @tenzen-y

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 6, 2025
@mimowo
Copy link
Contributor Author

mimowo commented Mar 6, 2025

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants