Last Modified: Oct 19, 2025
Affected Product(s):
F5OS Velos
Fixed In:
F5OS-A 1.4.0, F5OS-A 1.2.0
Opened: May 25, 2022 Severity: 3-Major
When the system date is changed, some of the k3s cluster certificates becomes invalid, and pods enter into an unknown/non-operational state. Once the system date and time are made current, most pods will be recovered. Some of the virt-controller/virt-operator/virt-api kubevirt pods are in a failed state but tenant functionality is not affected.
Some of the k3s pods go into a failed/non-operational state.
System date and time is changed back and forth.
Re-spinning the certificates will restore the pods. Delete the pods to trigger a re-spin of certificates that are in a terminating or crashed state. The orchestration manager will start the pod with a new certificate. Command to delete the pod: #kubectl delete pod <pod-name> -n <name-space>
Only change the system date and time when necessary.