Closed moshloop closed 1 month ago
And this pod that has started, but turned not ready - i.e. Status should be Not Ready with warning health (Unknown if the start time is < readinessProbe.initialDelaySeconds + ( (periodSeconds + timeoutSeconds) * failureThreshold
status:
phase: Running
podIP: 10.0.179.6
hostIP: 10.0.179.6
podIPs:
- ip: 10.0.179.6
hostIPs:
- ip: 10.0.179.6
qosClass: BestEffort
startTime: 2024-07-17T06:58:33Z
conditions:
- type: PodReadyToStartContainers
status: "True"
- type: Initialized
status: "True"
- type: Ready
status: "False"
- type: ContainersReady
status: "True"
- type: PodScheduled
status: "True"
containerStatuses:
- name: eks-pod-identity-agent
image: 602401143452.dkr.ecr.eu-west-1.amazonaws.com/eks/eks-pod-identity-agent:0.1.10
ready: true
state:
running:
startedAt: 2024-07-17T06:58:43Z
imageID: 602401143452.dkr.ecr.eu-west-1.amazonaws.com/eks/eks-pod-identity-agent@sha256:9cf48154b1603963d449f80ed8bc150918509ac025e92cdd67748a9f3f8ad367
started: true
lastState: {}
containerID: containerd://8e48835f5f3765827aed1470ef5a95312345c52a1a5c3db24ff800c8e10a6424
restartCount: 0
initContainerStatuses:
- name: eks-pod-identity-agent-init
image: 602401143452.dkr.ecr.eu-west-1.amazonaws.com/eks/eks-pod-identity-agent:0.1.10
ready: true
state:
terminated:
reason: Completed
exitCode: 0
startedAt: 2024-07-17T06:58:37Z
finishedAt: 2024-07-17T06:58:37Z
containerID: containerd://16032f42f71448ef31794b6805cb69f25cc4e59fd83622d3fa9b3acd00a3867c
imageID: 602401143452.dkr.ecr.eu-west-1.amazonaws.com/eks/eks-pod-identity-agent@sha256:9cf48154b1603963d449f80ed8bc150918509ac025e92cdd67748a9f3f8ad367
started: false
lastState: {}
containerID: containerd://16032f42f71448ef31794b6805cb69f25cc4e59fd83622d3fa9b3acd00a3867c
restartCount: 0
Scraped at: 2024-07-18T19:31:46.307804+00:00"