-
Notifications
You must be signed in to change notification settings - Fork 4.7k
kubelet: Wait less for control-plane pods to restart #17510
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
/test pull-kops-e2e-kubernetes-azure |
eb805d2
to
ecd8b8a
Compare
/test pull-kops-e2e-kubernetes-azure |
ecd8b8a
to
e959dba
Compare
/test pull-kops-e2e-kubernetes-azure |
TIL we can introduce alpha features in the kOps API. |
e959dba
to
0402ae9
Compare
/test pull-kops-e2e-kubernetes-azure |
/retest |
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-sigs/prow repository. |
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.
I like this idea. Unsure whether we should put it into the schema yet, but I'm definitely in favor of setting this on the control plane. (We could also look at an initContainer that waits for our dependencies)
@@ -242,6 +244,9 @@ func buildKubeletComponentConfig(kubeletConfig *kops.KubeletConfigSpec, provider | |||
if providerID != "" { | |||
componentConfig.ProviderID = providerID | |||
} | |||
componentConfig.CrashLoopBackOff = kubelet.CrashLoopBackOffConfig{ |
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.
Nit: should we mirror the kubelet config structure here (i.e. kubelet.crashLoopBackOff.maxContainerRestartPeriod, instead of kubelet.crashLoopBackOffMaxContainerRestartPeriod)?
if c.FeatureGates == nil { | ||
c.FeatureGates = make(map[string]string) | ||
} | ||
c.FeatureGates["KubeletCrashLoopBackOffMax"] = "true" |
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.
Do we think KubeletCrashLoopBackOffMax is going to land? Because if we're not sure, we might not want to expose it in the kubelet config yet
/cc @justinsb @rifelpet @ameukam
/hold for feedback