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.

Sign up for GitHub

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

Jump to bottom

[proposal] Support the resource management for Mid-tier pods. #1442

Open
2 of 4 tasks
saintube opened this issue Jul 4, 2023 · 6 comments · May be fixed by #1984
Open
2 of 4 tasks

[proposal] Support the resource management for Mid-tier pods. #1442

saintube opened this issue Jul 4, 2023 · 6 comments · May be fixed by #1984
Labels
area/koordlet kind/proposal Create a report to help us improve
Milestone
v1.6

Comments

@saintube
Copy link
Member

saintube commented Jul 4, 2023 •
edited

What is your proposal:

Support the resource management for Mid-tier pods in the koordlet:

Why is this needed:

The #1361 adds the Mid-tier resource, allowing a pod with Mid priority class to allocate kubernetes.io/mid-cpu and kubernetes.io/mid-memory resources. However, the resource management of Mid-tier is not fully supported in the koordlet. For example, the koordlet does not set the related cgroups like cpu.cfs_quota_us for a Mid+BE pod.
@saintube saintube added the kind/proposal Create a report to help us improve label Jul 4, 2023
@saintube
Copy link
Member Author

saintube commented Jul 4, 2023

/area koordlet

@hormes hormes mentioned this issue Jul 11, 2023
Merged
@stale
Copy link

stale bot commented Oct 29, 2023

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close
    Thank you for your contributions.

@saintube
Copy link
Member Author

/remove-lifecycle stale

@stale stale bot removed the lifecycle/stale label Oct 30, 2023
@stale Stale
Copy link

stale bot commented Jan 28, 2024

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close
    Thank you for your contributions.

@saintube
Copy link
Member Author

/remove-lifecycle stale

@j4ckstraw
Copy link
Contributor

#1874 export mid resource metric

@saintube saintube added this to the v1.5 milestone Jan 30, 2024
@j4ckstraw j4ckstraw linked a pull request Apr 3, 2024 that will close this issue
Draft
3 tasks
@saintube saintube modified the milestones: v1.5, v1.6 Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/koordlet kind/proposal Create a report to help us improve
Projects
None yet
Milestone
v1.6
Development

Successfully merging a pull request may close this issue.

koordlet: add mid runtimehooks j4ckstraw/koordinator
2 participants
@j4ckstraw @saintube