Release 1.7
-
Admin updating the SPBM policy name in vCenter could cause confusions/inconsistencies. Link
-
Two or more PVs could show different policy names but with the same policy ID. Link
-
Node status becomes NodeReady from NodeNotSchedulable after Failover. Link
Release 1.6.5
- Node status becomes NodeReady from NodeNotSchedulable after Failover. Link
Release 1.5.7
- Node status becomes NodeReady from NodeNotSchedulable after Failover. Link
Kubernetes-Anywhere
- Destroying a Kubernetes cluster operation using Kubernetes-anywhere is flaky Link