If a pod exceeds its memory "limit" what signal is sent to the process – InterviewSolution

1.	If a pod exceeds its memory "limit" what signal is sent to the process?
Answer» SIGKILL as immediately terminates the container and spawns a new one with OOM error. The OS, if using a cgroup based containerisation (docker, rkt, etc), will do the OOM killing. Kubernetes simply sets the cgroup limits but is not ultimately responsible for killing the processes.`SIGTERM` is sent to PID 1 and K8S waits for (default of 30 seconds) `terminationGracePeriodSeconds` before sending the `SIGKILL` or you can change that TIME with terminationGracePeriodSeconds in the pod. As LONG as your container will EVENTUALLY exit, it should be fine to have a long grace period. If you want a graceful restart it would have to do it inside the pod. If you don't want it killed, then you shouldn't SET a memory `limit` on the pod and there's not a way to disable it for the whole node. Also, when the liveness probe fails, the container will SIGTERM and SIGKILL after some grace period.

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.