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

[proposal] runtime-hooks should support multiple running mode #120

Closed
zwzhang0107 opened this issue May 5, 2022 · 2 comments · Fixed by #319
Closed

[proposal] runtime-hooks should support multiple running mode #120

zwzhang0107 opened this issue May 5, 2022 · 2 comments · Fixed by #319
Assignees
Labels
Milestone

Comments

@zwzhang0107
Copy link
Contributor

zwzhang0107 commented May 5, 2022

What is your proposal:
injections in runtime hooks of koordlet such as cpu qos,memory oqs,llc/mba can work with or without runtime-hook-manager(runtime-porxy mode)

Why is this needed:
someone would rather use bypass-injection mode than changing kubelet cri endpoint config.

Is there a suggested solution, if so, please add it:
runtime hooks in koordlet should support two running mode: injection(with cri proxy),bypass(without cri proxy)

@zwzhang0107 zwzhang0107 added the kind/proposal Create a report to help us improve label May 5, 2022
@zwzhang0107
Copy link
Contributor Author

/area koordlet
/area runtime

@zwzhang0107
Copy link
Contributor Author

/assign zwzhang0107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants