You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the /livez for LivenessProbe and /readyz for StartupProbe, this is This works for etcd >= v3.5.11, kubeadm has already applied this change, I think the same can be applied on karmada side.
basicly /livez = /health?exclude=NOSPACE&serializable=true and /readyz=/health?serializable=false
Can other components of Karmada make the same modifications?
Absolutely!
This makes sense for all components, but given that we recently completed the specification of metrics and health detection port parameters #5219, I don't think livez and readyz standardization for karmada components will happen too soon, at least not until version 1.12.
What would you like to be added:
Using the
/livez
for LivenessProbe and/readyz
for StartupProbe, this is This works for etcd >= v3.5.11, kubeadm has already applied this change, I think the same can be applied on karmada side.basicly/livez
=/health?exclude=NOSPACE&serializable=true
and/readyz
=/health?serializable=false
The design for the new probes is documented in etcd livez and readyz probes
releated:
Tasks:
Why is this needed:
This is more in line with the kubernetes style.
The text was updated successfully, but these errors were encountered: