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
In order to upgrade/migrate from MKE3 --> MKE4, Calico KDD must be enabled. However, at present we do not identify this pre-req on the Migrate from MKE 3.x doc page, nor do we provide instructions as to how to enable KDD in MKE3
Calico KDD (Kubernetes Datastore Driver) must be enabled (see Calico Docs for details on Calico KDD) prior to migrating from MKE3. To enable Calico KDD:
Ensure MKE has been upgraded to 3.7.12 or later (option to enable Calico KDD was first exposed with this release)
Set calico_kdd = true in the cluster_config section of the the MKE3 configuration file
Upload the MKE3 configuration file to apply the configuration change
Note: Converting the Calico datastore from etcd to KDD may take up to 30 minutes, depending on the size of the cluster. Upon successful completion, the following output will be displayed in the console:
{"message":"Calico datastore migration from etcd to kdd successful"}
...
The text was updated successfully, but these errors were encountered:
Description
In order to upgrade/migrate from MKE3 --> MKE4, Calico KDD must be enabled. However, at present we do not identify this pre-req on the Migrate from MKE 3.x doc page, nor do we provide instructions as to how to enable KDD in MKE3
URL of the page
Migrate from MKE 3.x
What we have currently
n/a - missing content
Suggested Edit
Prerequisites
...
Calico KDD (Kubernetes Datastore Driver) must be enabled (see Calico Docs for details on Calico KDD) prior to migrating from MKE3. To enable Calico KDD:
calico_kdd = true
in thecluster_config
section of the the MKE3 configuration fileNote: Converting the Calico datastore from etcd to KDD may take up to 30 minutes, depending on the size of the cluster. Upon successful completion, the following output will be displayed in the console:
{"message":"Calico datastore migration from etcd to kdd successful"}
...
The text was updated successfully, but these errors were encountered: