Initial delay ustawiony mam domyślnie, czyli 50 sekund na readiness check i 120 sekund na liveness check.
Wynik polecenia describe:
Name: wpe-rest-69b7b7fcf6-lmdlv
Namespace: ezd
Priority: 0
Service Account: ezdrp
Node: ezd-test/172.21.63.62
Start Time: Tue, 16 Jul 2024 07:23:13 +0000
Labels: app=ezdrpapp-wpe-rest
environment=Development
pod-template-hash=69b7b7fcf6
role=backend
Annotations: cni.projectcalico.org/containerID: d2fc36d3df28a80ddf5b7c90d1bc61ad53337afef482dce6756ca2a43efc31d1
cni.projectcalico.org/podIP: 10.42.0.185/32
cni.projectcalico.org/podIPs: 10.42.0.185/32
Status: Running
IP: 10.42.0.185
IPs:
IP: 10.42.0.185
Controlled By: ReplicaSet/wpe-rest-69b7b7fcf6
Init Containers:
volume-owner-hack:
Container ID: containerd://67047e67fdbf07420b0ea1c29bf80a4d94adada08df35bbf64e8ad60564aec4b
Image: busybox
Image ID: docker.io/library/busybox@sha256:9ae97d36d26566ff84e8893c64a6dc4fe8ca6d1144bf5b87b2b85a32def253c7
Port: <none>
Host Port: <none>
Command:
sh
-c
chown -R 501:501 /data
State: Terminated
Reason: Completed
Exit Code: 0
Started: Tue, 16 Jul 2024 07:23:15 +0000
Finished: Tue, 16 Jul 2024 07:23:15 +0000
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/data from wpe-rest-storage (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ssq2m (ro)
Containers:
wpe-rest:
Container ID: containerd://8cbb86f3953334f32e9c450b69a90cae785f39834c1a6d92771313d973d6be0d
Image: hub.eadministracja.nask.pl/ezdrp/wpe-rest:19.7.38
Image ID: hub.eadministracja.nask.pl/ezdrp/wpe-rest@sha256:48b56774937398d3da78b72b5da5b9cee5068f5f99dfccc03979fd781b72c6fd
Port: <none>
Host Port: <none>
State: Running
Started: Tue, 16 Jul 2024 07:56:44 +0000
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Tue, 16 Jul 2024 07:53:35 +0000
Finished: Tue, 16 Jul 2024 07:56:43 +0000
Ready: False
Restart Count: 9
Limits:
cpu: 2
memory: 8000Mi
Requests:
cpu: 200m
memory: 756Mi
Liveness: http-get http://:8080/http://wpe-rest/info delay=120s timeout=1s period=10s #success=1 #failure=4
Readiness: http-get http://:8080/http://wpe-rest/info delay=50s timeout=1s period=10s #success=1 #failure=2
Environment: <none>
Mounts:
/data from wpe-rest-storage (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ssq2m (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
wpe-rest-storage:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: wpe-rest-storage
ReadOnly: false
kube-api-access-ssq2m:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 34m default-scheduler Successfully assigned ezd/wpe-rest-69b7b7fcf6-lmdlv to ezd-test
Normal Pulling 34m kubelet Pulling image "busybox"
Normal Pulled 34m kubelet Successfully pulled image "busybox" in 958ms (958ms including waiting)
Normal Created 34m kubelet Created container volume-owner-hack
Normal Started 34m kubelet Started container volume-owner-hack
Normal Pulled 34m kubelet Container image "hub.eadministracja.nask.pl/ezdrp/wpe-rest:19.7.38" already present on machine
Normal Created 34m kubelet Created container wpe-rest
Normal Started 34m kubelet Started container wpe-rest
Warning Unhealthy 32m (x4 over 32m) kubelet Liveness probe failed: Get "http://10.42.0.185:8080/info": dial tcp 10.42.0.185:8080: connect: connection refused
Warning Unhealthy 9m33s (x142 over 33m) kubelet Readiness probe failed: Get "http://10.42.0.185:8080/info": dial tcp 10.42.0.185:8080: connect: connection refused
Warning BackOff 4m34s (x25 over 9m23s) kubelet Back-off restarting failed container wpe-rest in pod wpe-rest-69b7b7fcf6-lmdlv_ezd(eb618073-b00d-4b1b-a798-58d7b7b5590e)