-
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
[FG:InPlacePodVerticalScaling] Implement version skew handling for in-place pod resize #117767
Comments
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. |
/sig node |
@vinaykul: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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. |
/assign |
Hello @infdahai infdahai, are you working on this? |
According to description of pr. The changes are documented but implementation is still remaining, right? |
@Sajiyah-Salat yeah, I just quit this. |
can I work on this issue? |
you can just use |
/assign |
@carlory , seem like you have experienced in contributing upstream, do you want to give the chance to others for |
/unassign |
/assign |
/assign |
/assign |
Hey everyone. Just saw this issue assigned to multiple people. Was curious to know if someone is working on it or is it up for grabs? |
@vinaykul can you explain how to tackle with this issue? |
/assign |
/assign |
/assign |
/assign |
/assign |
/assign |
I don't understand the description (sorry for that, I'm a new contributor) (@vinaykul for visibility)
Is it a desired state description or a current state? If a current state, then what should be a desired behavior here? |
I've fixed (I guess) the first part in |
@vinaykul hi, could you take a look? Or point out somebody who can take it over from you if you're not available? |
/assign |
@Shrihariii dunno if it makes sense for you to work on it - there is already an open pull request and discussion in it is going on. |
/assign |
/assign |
@SequoiaGod: GitHub didn't allow me to assign the following users: SequoiaGod. Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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-sigs/prow repository. |
To anyone still working on this issue, |
What would you like to be added?
This is a tracking bug to implement two changes to better handle version skew as documented in https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1287-in-place-update-pod-resources#version-skew-strategy
Why is this needed?
This is needed to gracefully handle component version skews that can occur during upgrades.
The text was updated successfully, but these errors were encountered: