-
Notifications
You must be signed in to change notification settings - Fork 14
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
Insert Calico KDD into the migrate topic prerequisites. #242
base: main
Are you sure you want to change the base?
Conversation
@moshiurH @rleap-m - could you please take a look in light of my comments here. I feel we need to emphasize the latest release and de-emphasize 3.7.12. Also what I found regarding the total time is approximately a node done every 10 seconds - so I feel the time value given here needs to be revised accordingly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One issue with the writeup, otherwise everything else looks good!
4. Apply the modified MKE 3 configuration file: | ||
|
||
```shell | ||
mkectl apply -f <mke-configuration-file>.yaml |
There was a problem hiding this comment.
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"}
completion, the following confirmation will display: | ||
|
||
```shell | ||
{"message":"Calico datastore migration from etcd to kdd successful"} |
There was a problem hiding this comment.
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:
- We should mention that migration to kdd mode is an irreversible process once it is completed successfully
- 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."
No description provided.