Perform a Safe Rolling Update of a Kubernetes Deployment
Learn how to update a Deployment’s container image with zero downtime by using kubectl, verifying the rollout, and reverting if needed.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to update a Deployment’s container image with zero downtime by using kubectl, verifying the rollout, and reverting if needed.
I had the below YAML for my Ingress and it worked (and continues to work): apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: test-ingress namespace: test-layer annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: mylocalhost.com http: paths: - path: / backend: serviceName: test-app servicePort: 5000 However, it
I try to install gke-gcloud-auth-plugin on a Mac M1 with zsh, following the gcloud docs . The installation ran without issue and trying to re-run gcloud components install gke-gcloud-auth-plugin I get the All components are up to date. message. However, gke-gcloud-auth-plugin --version returns zsh: command not found: gke-gcloud-auth-plugin . kubectl , instal
I have kubernetes pods running as shown in command "kubectl get all -A " : and same pods are shown in command "kubectl get pod -A" : I want to enter/login to any of these pod (all are in Running state). How can I do that please let me know the command?
I started using Lens and noticed that it gives you some warnings when the pods inside the nodes have limits higher than the actual capacity. So I tried to get this information with kubectl but I'm new to jsonpath and I just managed to get the raw info using something like this: kubectl get pods -o=jsonpath='{.items..resources.limits}' -A That produces someth
After upgrading to v1.24.0 (after Dockershim removal), I had to install cri-dockerd , then I did the following: sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --cri-socket=unix:///var/run/cri-dockerd.sock --apiserver-advertise-address=192.168.0.196 I have chosen flannel as Network Plugin: kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/
I'm beginning to build out a kubernetes cluster for our applications. We are using Azure for cloud services, so my K8s cluster is built using AKS. The AKs cluster was created using the portal interface for Azure. It has one node, and I am attempting to create a pod with a single container to deploy to the node. Where I am stuck currently is trying to connect
Cannot install the helm chart but when I use raw file generated by helm, I am able to install via kubectl apply. Following error is displayed when i use helm install myChart . --debug Error: cannot re-use a name that is still in use helm.go:88: [debug] cannot re-use a name that is still in use helm.sh/helm/v3/pkg/action.(*Install).availableName helm.sh/helm/
Everything was running smoothly with my Kubernetes clusters until today: after performing an update on my Ubuntu system, I'm now unable to establish a connection from my working environment to the kubernetes clusters. When executing the command kubectl get pods , I'm encountering the following error message: E0805 09:59:45.750534 234576 memcache.go:265] coul
Asked · 12 Mar 2026, 14:14 UTC
answered · 15 Mar 2026, 14:14 UTC
answered · 28 Jun 2025, 05:57 UTC
answered · 12 Dec 2024, 09:04 UTC