What is the impact of upgrading kubelet if we leave the pods on the wo – InterviewSolution

InterviewSolution

1.	What is the impact of upgrading kubelet if we leave the pods on the worker node - will it break running pods? why?
Answer» Restarting KUBELET, which has to happen for an upgrade will cause all the Pods on the NODE to stop and be started again. It’s generally better to drain a node because that way Pods can be gracefully migrated, and things like Disruption Budgets can be honored. The problem is that `kubectl` keeps up with the state of all running pods, so when it GOES away the CONTAINERS don’t necessarily die, but as soon as it comes back up, they are all killed so `kubectl` can create a clean slate. As kubelet communicates with the apiserver, so if something happens in between of upgrade process, rescheduling of pods may take place and health checks may fail in between the process. During the restart, the kubelet will stop querying the API, so it won’t start/stop containers, and Heapster won’t be able to fetch system metrics from cAdvisor. Just make sure it’s not down for too long or the node will be removed from the CLUSTER!

Discussion

No Comment Found

Related InterviewSolutions

If you have a pod that is using a ConfigMap which you updated, and you want the container to be updated with those changes, what should you do?
When deploying you will get an error of mounting as read-only, which is effecting to fluent to read some of the mentioned sources in the configmap.how can we avoid this read-only error?
volumeMounts:name: fluentdmountPath: /fluentd/etcname: varlogmountPath: /var/logname: container1mountPath: /var/lib/docker/containersreadOnly: truesecurityContext:privileged: trueterminationGracePeriodSeconds: 30volumes:name: varloghostPath:path: /var/logname: container1hostPath:path: /var/lib/docker/containersname: fluentdconfigMap:name: fluentd-config
I have a configmap for 3 files that are going to be mounted in supposing "fluentd/etc/" and the respective files would be fluent.conf, kubernetes.conf, systemd.conf, config map in deployment.yaml is like this
How to configure a default ImagePullSecret for any deployment?
How should you connect an app pod with a database pod?
Does the container restart When applying/updating the secret object (kubectl apply -f mysecret.yml)? If not, how is the new password applied to the database?
How service that selects apps based on the label and has an externalIP?
What is the impact of upgrading kubelet if we leave the pods on the worker node - will it break running pods? why?
If I have multiple containers running inside a pod, and I want to wait for a specific container to start before starting another one.