-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
If k8s support update resource on the fly #116636
Comments
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
Please see the group list for a listing of the SIGs, working groups, and committees available. 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. |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/kind support kubernetes/enhancements#1287 captures the state of that enhancement. You can also view details in https://www.k8s.dev/resources/keps/ |
This was a true statement |
Can kubernetes/enhancements # 1287 work normally? If this can run normally, I think this KEP has implemented in-place updates. My understanding is that the function can be implemented now, but it has not been merged into a K8s version that can be released. Am I right? If not, what is the reason why in-place update cannot be performed at present? Thanks! |
GitHub is not the right place for support requests. If you're looking for more help, check Server Fault. You can also post on the Kubernetes Slack or the Discuss Kubernetes forum. /close |
@sftim: Closing this issue. In response to this:
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. |
What would you like to be added?
Features of in-place update resource in K8s.
Why is this needed?
Adjust the pod resource on the fly is essential for lots of applications
Does K8s support in-place autoscaling, which means update cpu resource on the fly. I want to change the cpu utilization of a pod without any termination(restarting or evcting).
I have look for this anwser for a long time. I see that the enhancement in K8s mentioning it is achieved in K8s, but when I asked this issue in slack of sig-autoscaling, they told me it is not achieved now as in the PR, and it waits for other components(like kubelet or CRI) to supports auto-scaling on the fly.
Now I can’t tell whether K8s supports in-place autoscaling or not. Who can tell me the exact answer?
Thanks a lot!
The text was updated successfully, but these errors were encountered: