Do rolling updates declared with a deployment take effect if I manuall

1.	Do rolling updates declared with a deployment take effect if I manually delete pods of the replica set with kubectl delete pods or with the dashboard? Will the minimum required a number of pods be maintained?
Answer» YES, the scheduler will make sure (as long as you have the correct resources) that the number of desired pods are met. If you delete a pod, it will recreate it. Also deleting a SERVICE won't delete the Replica set. if you remove Service or deployment you want to remove all resources which Service created. Also having a single replica for a deployment is usually not recommended because you cannot scale out and are treating in a specific way Any app should be `Ingress` -> `Service` -> `Deployment` -> (volume mount or 3rd-party cloud storage) You can skip ingress and just have `LoadBalancer (service)` -> `Deployment` (or Pod but they don't auto RESTART, DEPLOYMENTS do)

Do rolling updates declared with a deployment take effect if I manually delete pods of the replica set with kubectl delete pods or with the dashboard? Will the minimum required a number of pods be maintained?

Answer»

YES, the scheduler will make sure (as long as you have the correct resources) that the number of desired pods are met. If you delete a pod, it will recreate it. Also deleting a SERVICE won't delete the Replica set. if you remove Service or deployment you want to remove all resources which Service created. Also having a single replica for a deployment is usually not recommended because you cannot scale out and are treating in a specific way

Any app should be `Ingress` -> `Service` -> `Deployment` -> (volume mount or 3rd-party cloud storage)

You can skip ingress and just have `LoadBalancer (service)` -> `Deployment` (or Pod but they don't auto RESTART, DEPLOYMENTS do)

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.