This is a Bug Report
Problem:
Section: Roll back an update is out of date
https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/#roll-back-an-update
After pulling the non-existent image for deployment kubectl describe pods does not have an Events section. I had to find the event with kubectl get events instead.
sarena.meas@IONQ-D828:~$ kubectl describe pods
Name: kubernetes-bootcamp-68cf47c9c8-6xj6q
Namespace: default
Priority: 0
Service Account: default
Node: minikube/192.168.49.2
Start Time: Wed, 17 Jun 2026 22:55:19 -0700
Labels: app=kubernetes-bootcamp
pod-template-hash=68cf47c9c8
Annotations: <none>
Status: Running
IP: 10.244.0.18
IPs:
IP: 10.244.0.18
Controlled By: ReplicaSet/kubernetes-bootcamp-68cf47c9c8
Containers:
kubernetes-bootcamp:
Container ID: docker://b5c40eec972d4918739bd46352fc2f950e8cc77217b7dcd86027852c2e1209a3
Image: docker.io/jocatalin/kubernetes-bootcamp:v2
Image ID: docker-pullable://jocatalin/kubernetes-bootcamp@sha256:fb1a3ced00cecfc1f83f18ab5cd14199e30adc1b49aa4244f5d65ad3f5feb2a5
Port: <none>
Host Port: <none>
State: Running
Started: Wed, 17 Jun 2026 22:55:21 -0700
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5dmhn (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
kube-api-access-5dmhn:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
Optional: false
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Name: kubernetes-bootcamp-68cf47c9c8-kjl62
Namespace: default
Priority: 0
Service Account: default
Node: minikube/192.168.49.2
Start Time: Wed, 17 Jun 2026 22:55:21 -0700
Labels: app=kubernetes-bootcamp
pod-template-hash=68cf47c9c8
Annotations: <none>
Status: Running
IP: 10.244.0.19
IPs:
IP: 10.244.0.19
Controlled By: ReplicaSet/kubernetes-bootcamp-68cf47c9c8
Containers:
kubernetes-bootcamp:
Container ID: docker://7b56567d6511561ab484d353bd0caa90215534dabe42135da2f9c99d50bad0e7
Image: docker.io/jocatalin/kubernetes-bootcamp:v2
Image ID: docker-pullable://jocatalin/kubernetes-bootcamp@sha256:fb1a3ced00cecfc1f83f18ab5cd14199e30adc1b49aa4244f5d65ad3f5feb2a5
Port: <none>
Host Port: <none>
State: Running
Started: Wed, 17 Jun 2026 22:55:22 -0700
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-jf2g5 (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
kube-api-access-jf2g5:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
Optional: false
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Name: kubernetes-bootcamp-845bc89d75-9vjtj
Namespace: default
Priority: 0
Service Account: default
Node: minikube/192.168.49.2
Start Time: Thu, 18 Jun 2026 00:01:04 -0700
Labels: app=kubernetes-bootcamp
pod-template-hash=845bc89d75
Annotations: <none>
Status: Pending
IP: 10.244.0.21
IPs:
IP: 10.244.0.21
Controlled By: ReplicaSet/kubernetes-bootcamp-845bc89d75
Containers:
kubernetes-bootcamp:
Container ID:
Image: gcr.io/google-samples/kubernetes-bootcamp:v10
Image ID:
Port: <none>
Host Port: <none>
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-66hks (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-66hks:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
Optional: false
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Proposed Solution:
Page to Update:
https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/#roll-back-an-update
I have the following versions:
sarena.meas@IONQ-D828:~$ minikube version
minikube version: v1.38.1
commit: c93a4cb9311efc66b90d33ea03f75f2c4120e9b0
sarena.meas@IONQ-D828:~$ kubectl version
Client Version: v1.36.2
Kustomize Version: v5.8.1
Server Version: v1.35.1
This is a Bug Report
Problem:
Section: Roll back an update is out of date
https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/#roll-back-an-update
After pulling the non-existent image for deployment
kubectl describe podsdoes not have anEventssection. I had to find the event withkubectl get eventsinstead.Proposed Solution:
Page to Update:
https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/#roll-back-an-update
I have the following versions: