You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per @vikramhh in BOP-1697, support for the kube-router CNI in v4.0.1 is limited to fresh installs only. This means that if a v4.0.1 cluster is already running with the Calico CNI, it is not possible to migrate the MKE4 config from using the Calico CNI to using the kube-router CNI.
To attempt such a CNI migration is unsupported in v4.0.1. This also applies to any cluster upgraded from v4.0.0 → v4.0.1.
The text was updated successfully, but these errors were encountered:
As first submitted by @quadespresso in https://mirantis.jira.com/browse/ENGDOCS-2573.
Support for the kube-router CNI is new as of MKE v4.0.1.
Per @vikramhh in BOP-1697, support for the kube-router CNI in v4.0.1 is limited to fresh installs only. This means that if a v4.0.1 cluster is already running with the Calico CNI, it is not possible to migrate the MKE4 config from using the Calico CNI to using the kube-router CNI.
To attempt such a CNI migration is unsupported in v4.0.1. This also applies to any cluster upgraded from v4.0.0 → v4.0.1.
The text was updated successfully, but these errors were encountered: