Bug ID 1581077: A blade may fail to join the Kubernetes cluster if another blade is offline.

Last Modified: Jun 29, 2026

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

Known Affected Versions:
F5OS-C 1.5.1, F5OS-C 1.6.2, F5OS-C 1.6.4

Opened: Apr 23, 2024

Severity: 2-Critical

Symptoms

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.

Impact

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.

Conditions

This can happen when an existing blade in the Kubernetes cluster is offline, or in a failed state.

Workaround

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.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips