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.

Sign up for GitHub

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

Jump to bottom

Insert Calico KDD into the migrate topic prerequisites. #242

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Insert Calico KDD into the migrate topic prerequisites. #242

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions content/docs/migrate-from-MKE-3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,30 @@ Verify that you have the following components in place before you begin upgradin
keyPath: <path-to-ssh-key>
```

- Calico KDD (Kubernetes Datastore Driver), enabled:

1. Verify that the MKE 3.x instance being upgraded to MKE 4 is 3.7.12 or
later.

2. Obtain the MKE 3 configuration file.

3. In the `cluster_config` section of the MKE 3 configuration file, set the
`calico_kdd` parameter to `true`.

4. Apply the modified MKE 3 configuration file:

```shell
mkectl apply -f <mke-configuration-file>.yaml
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mkectl commands are used to modify the MKE 4 configurations only.

To modify mke 3 configurations, we will need to perform the following bash commands to apply the new TOML configurations (which can be found in the mke 3 documentation for working with toml):

$ AUTHTOKEN=$(curl --silent --insecure --data '{"username":"'$MKE_USERNAME'","password":"'$MKE_PASSWORD'"}' https://$MKE_HOST/auth/login | jq --raw-output .auth_token)
$ curl --silent --insecure -X PUT -H "accept: application/toml" -H "Authorization: Bearer $AUTHTOKEN" --upload-file 'mke-config.toml' https://$MKE_HOST/api/ucp/config-toml
{"message":"Calico datastore migration from etcd to kdd successful"}

```

{{< callout type="info" >}} The conversion of the Calico datastore from etcd to
KDD may take up to 30 minutes, depending on the size of the cluster. On
completion, the following confirmation will display:

```shell
{"message":"Calico datastore migration from etcd to kdd successful"}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KoryKessel-Mirantis @rleap-m @vikramhh
Based on Vikram's suggestions, maybe we should add a disclaimer for point 7 and 8:

  1. We should mention that migration to kdd mode is an irreversible process once it is completed successfully
  2. We should also mention that in case an enterprise cluster needs to be migrated, a ticket should be opened with Mirantis so that the process can be planned and monitored during execution to reduce risk

Something like: "Please note that migration to kdd mode is an irreversible process once it is completed successfully. For migrating enterprise cluster, a ticket should be opened with Mirantis so that the process can be planned and monitored during execution to reduce risk."

```

## Migrate configuration

In migrating to MKE 4 from MKE 3, you can directly transfer settings using `mkectl`.
Expand Down