When certificates are issued, Istio-controlled pods need to be bounced (restarted) to ensure they pick up the new certificates due to this issue. The certificate issuer will create a PodBounceDirective containing the namespaces and labels of the pods that need to be bounced in order to pick up the new certs.
A list of Kubernetes pods to bounce (delete and cause a restart) when the certificate is issued. This will include the control plane pods as well as any Pods which share a data plane with the target mesh.
Wait for this number of replacement pods to reach be fully ready before deleting the next set of selected Pods. This is used to ensure the control plane pods are allowed to restart before sidecars and gateways are restarted.
PodBounceDirectiveStatus reports the status for stateful Pod bounces (when bouncing pods requires waiting for readiness).
Field
Type
Label
Description
observedGeneration
int64
The most recent generation observed in the the PodBounceDirective metadata. If the observedGeneration does not match metadata.generation, the Gloo Mesh agent has not processed the most recent version of this IssuedCertificate.
A list of Kubernetes pods to bounce (delete and cause a restart) when the certificate is issued. This will include the control plane pods as well as any Pods which share a data plane with the target mesh.
PodBounceDirectiveStatus.BouncedPodSet
A set of pods that were restarted.
Field
Type
Label
Description
bouncedPods
[]string
repeated
The names of the pods that were bounced for the corresponding selector specified in PodBounceDirectiveSpec.PodSelector.labels.
PodBounceDirectiveStatus.State
Possible states in which an PodBounceDirective can exist.
Name
Number
Description
PENDING
0
The PodBounceDirective has yet to be picked up by the agent.
BOUNCING_PODS
1
The agent has decided on which pods to bounce, and it's working on it.
FAILED
3
Processing the pod bounce directive workflow failed.