Bug ID 1188877: Kubernetes Cluster Reinstall provision extended from VELOS to rSeries

Last Modified: Jun 04, 2025

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

Fixed In:
F5OS-A 1.7.0

Opened: Nov 11, 2022

Severity: 3-Major

Symptoms

In some cases, it is necessary to reinstall the K3S cluster on the appliances. On VELOS, there is a easy way to reinstall the Kubernetes cluster by creating the flag "touch /var/omd/CLUSTER_REINSTALL". Starting with the F50S-A 1.6.0 release, we extended this provision to rSeries appliances.

Impact

Existing tenants will be moved back to a Configured state and traffic will be interrupted. New tenants won't get deployed until the cluster is installed properly.

Conditions

It is recommended to reinstall the cluster as the last measure if there are any issues with tenant deployment/running.

Workaround

The cluster reinstall feature is usually the mitigation/workaround.

Fix Information

To initiate cluster reinstall, do: touch /var/omd/CLUSTER_REINSTALL (needs root access)

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips