[proposal] move `memory qos` plugin as runtime hook plugin

[zwzhang0107]

What is your proposal: Plugins in qos manager can be classified into two types: static and dynamic.

For dynamic type, pod will be adjusted dynamically according to node running state, such as cpu suppress, cpu burst, memory evict. Dynamic type strategies has been refactored as plugin in https://github.com/koordinator-sh/koordinator/pull/1500.

For static type, advanced parameters like NodeSLO will be injected according to pod QoS and Priority, such as cpu qos, memory qos.

Why is this needed: move static type to runtime hook to make sure that qos parameters in can be set ASAP once container created

Is there a suggested solution, if so, please add it:

[zwzhang0107]

/milestone v1.2 /assign zwzhang0107

[zwzhang0107]

/area koordlet

[zwzhang0107]

consider some container may have ignore_resource property

[stale[bot]]

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.

[stale[bot]]

This issue has been automatically closed 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:
• Reopen this PR with /reopen Thank you for your contributions.

[zwzhang0107]

/reopen

[koordinator-bot[bot]]

@zwzhang0107: Reopened this issue.

In response to this:

/reopen

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.