Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Calico KDD needed as an additional MKE3 migration prerequisite #232

Closed
rleap-m opened this issue Nov 22, 2024 · 2 comments · Fixed by #242
Closed

Enable Calico KDD needed as an additional MKE3 migration prerequisite #232

rleap-m opened this issue Nov 22, 2024 · 2 comments · Fixed by #242

Comments

@rleap-m
Copy link
Collaborator

rleap-m commented Nov 22, 2024

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:

    1. Ensure MKE has been upgraded to 3.7.12 or later (option to enable Calico KDD was first exposed with this release)
    2. Obtain an MKE3 configuration file
    3. Set calico_kdd = true in the cluster_config section of the the MKE3 configuration file
    4. 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"}
    ...

@rleap-m
Copy link
Collaborator Author

rleap-m commented Nov 22, 2024

This ticket is a duplicate of #231. Just didn't want things to get mixed up - if the other is applied first than this can be closed out. FYI @moshiurH @MagdaDziadosz @KoryKessel-Mirantis

@KoryKessel-Mirantis
Copy link
Collaborator

Ah. So we have battling PRs! OK. This should be curious.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants