Last Modified: Jul 15, 2026
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.5.1, F5OS-C 1.6.2, F5OS-C 1.6.4
Fixed In:
F5OS v2.0.0
Opened: Apr 23, 2024 Severity: 2-Critical
In pre F5OS-C v2.0 software version, if a blade is offline in the Kubernetes cluster and a new blade tries to join the Kubernetes cluster, the addition of the new blade to Kubernetes cluster will fail.
New blades will not be able to be added to the Kubernetes cluster, until the offline blade is either recovered or removed from the Kubernetes cluster.
This can happen when an existing blade in the Kubernetes cluster is offline, or in a failed state.
The workaround is to bring the failed blade back online in the cluster, or to remove the failed blade from the cluster. Once this done the new blade will be able to join the cluster.
With the upgrade to K3S in v2.0.0 and newer F5OS-C releases, it is no longer required to have all blades online in the cluster to add a new blade.