this repo has no description
Use storage-aware health probes for Zot registry
Liveness and readiness probes now hit /v2/_catalog?n=1 instead of /v2/,
which actually exercises the storage backend. The shallow /v2/ endpoint
returns 200 even when the JuiceFS mount is stale.
Startup probe threshold bumped to 60×5s to accommodate metadb parsing
over JuiceFS on cold starts.
+4
-4
+4
-4
k8s/registry/deployment.yaml
+4
-4
k8s/registry/deployment.yaml
···
41
41
httpGet:
42
42
path: /v2/
43
43
port: 5000
44
-
failureThreshold: 30
45
-
periodSeconds: 2
44
+
failureThreshold: 60
45
+
periodSeconds: 5
46
46
livenessProbe:
47
47
httpGet:
48
-
path: /v2/
48
+
path: /v2/_catalog?n=1
49
49
port: 5000
50
50
periodSeconds: 30
51
51
timeoutSeconds: 5
52
52
failureThreshold: 3
53
53
readinessProbe:
54
54
httpGet:
55
-
path: /v2/
55
+
path: /v2/_catalog?n=1
56
56
port: 5000
57
57
periodSeconds: 10
58
58
timeoutSeconds: 5