Bug ID 1188105: K3SClusterUpgrade status shown as Done before cluster pods running up on appliance

Last Modified: Feb 08, 2024

Affected Product(s):
F5OS F5OS(all modules)

Fixed In:
F5OS-A 1.7.0

Opened: Nov 09, 2022

Severity: 2-Critical

Symptoms

When an appliance upgrades the k3s (Lite Weight Kubernetes) to newer version, the K3S Cluster Upgrade status goes to Done state before bringing cluster pods up and running.

Impact

No functional impact. But the information published can be misleading.

Conditions

When Upgrade of K3S cluster gets triggered, the cluster upgrade status gets updated in ConfD before bringing cluster pods up.

Workaround

With K3sClusterupdate status also checks for the cluster pods status to see if the cluster came up properly.

Fix Information

Also check cluster pods status.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips