Last Modified: Oct 21, 2024
Affected Product(s):
F5OS F5OS
Known Affected Versions:
F5OS-A 1.4.0
Fixed In:
F5OS-A 1.8.0
Opened: Feb 24, 2023 Severity: 2-Critical
Upon changing the system date following things can be observed in the appliance 1. K3S cluster pods go into an errored state. 2. Cannot bring up the tenant on the Cluster
The K3S cluster does not come UP properly and eventually it brings down the tenant
Either by using an NTP server or by using CLI date/time can be changed. Changing the date forward and moving back to the original date.
Workaround: 1. Identify the pods which are having certificate issues. 2. In the case of the K3S cluster and kubevirt pods, It can be recovered by deleting the pods.
Check for pods in an errored state and delete using the following commands. kubectl delete pod <name> -n <namespace> --force