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

Can we design a more general thing replacing podqosensurancepolicies & nodeqosensurancepolicies? #45

Closed
yan234280533 opened this issue Dec 16, 2021 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@yan234280533
Copy link
Contributor

Can we design a more general thing replacing podqosensurancepolicies & nodeqosensurancepolicies?

Originally posted by @yufeiyu in #5 (comment)

@yan234280533
Copy link
Contributor Author

It good idea. Along the discuss resuIt before, we will more in-depth evaluate the similar proportions of podqosensurancepolicies and nodeqosensurancepolicies when we startup the design of pod qos ensurance.

@yan234280533 yan234280533 self-assigned this Dec 16, 2021
@yan234280533 yan234280533 added the question Further information is requested label Dec 16, 2021
@mfanjie
Copy link
Contributor

mfanjie commented Dec 27, 2021

I am thinking that workload SLO is not for QOS Ensurance only, it can also trigger scaling, we may need to thinking more

@qmhu qmhu closed this as completed Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants