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

If k8s support update resource on the fly #116636

Closed
xfyan0408 opened this issue Mar 15, 2023 · 7 comments
Closed

If k8s support update resource on the fly #116636

xfyan0408 opened this issue Mar 15, 2023 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/support Categorizes issue or PR as a support question. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@xfyan0408
Copy link

xfyan0408 commented Mar 15, 2023

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!

@xfyan0408 xfyan0408 added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 15, 2023
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 15, 2023
@k8s-ci-robot
Copy link
Contributor

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

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.

@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 15, 2023
@sftim
Copy link
Contributor

sftim commented Mar 15, 2023

/kind support

kubernetes/enhancements#1287 captures the state of that enhancement.

You can also view details in https://www.k8s.dev/resources/keps/

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Mar 15, 2023
@sftim
Copy link
Contributor

sftim commented Mar 15, 2023

they told me it is not achieved now

This was a true statement

@xfyan0408
Copy link
Author

they told me it is not achieved now

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!

@sftim
Copy link
Contributor

sftim commented Mar 28, 2023

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

@k8s-ci-robot
Copy link
Contributor

@sftim: Closing this issue.

In response to this:

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/support Categorizes issue or PR as a support question. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants