-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
Remove StreamingConnectionIdleTimeout
kubelet option
#122104
Conversation
Please note that we're already in Test Freeze for the Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Nov 29 10:04:55 UTC 2023. |
d3ed164
to
6a1c840
Compare
StreamingConnectionIdleTimeout
kubelet optionStreamingConnectionIdleTimeout
kubelet option
/approve |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kwilczynski, saschagrunert The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
StreamingConnectionIdleTimeout
kubelet optionStreamingConnectionIdleTimeout
kubelet option
StreamingConnectionIdleTimeout
kubelet optionStreamingConnectionIdleTimeout
kubelet option
if you remove the flags, systems that are deployed today setting the flag, are going to fail to run once they upgrade @liggitt you have always more experience with all these deprecations, any suggestions? |
https://kubernetes.io/docs/reference/using-api/deprecation-policy/
that is not true, do you have more examples, we have a strong commitment with not breaking users, |
@@ -80,7 +80,6 @@ seccompDefault: false | |||
serializeImagePulls: true | |||
shutdownGracePeriod: 0s | |||
shutdownGracePeriodCriticalPods: 0s | |||
streamingConnectionIdleTimeout: 4h0m0s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUIC this is a noop for a long time so this is correct
@kwilczynski let me clarify , I think that removing it is ok, I'm just arguing about how to do it, IIUIC this functionality does not work for the long time so the API change is a noop. However, if you remove the flag without previous announcement, if you have clusters with that flag set at the upgrade they will break, so I think that at least we should warn about this and add a release note about it so people prepare in advance. |
/lgtm one comment about the flag , I think is better if we agree on a release for the flag to be removed so we can inform end users in advance and prepare release notes and so on ... Thanks |
LGTM label has been added. Git tree hash: d0d8a377ebbb9e48c772ab9c2bf91d989afb563d
|
an example of potential end users that will have their cluster broken because we remove a flag without notice https://grep.app/search?q=--streaming-connection-idle-timeout |
The option is not used any more and the timeout is handled by the container runtime. Signed-off-by: Sascha Grunert <[email protected]>
725e6e6
to
f8785fc
Compare
New changes are detected. LGTM label has been removed. |
/test pull-kubernetes-conformance-kind-ga-only-parallel |
/triage accepted |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
PR needs rebase. 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. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closed this PR. 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. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The option is not used any more and the timeout is handled by the container runtime.
Removing the CLI because the kubelet already states:
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
cc @kwilczynski
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: