From a2b1e3fc08f2886b956b07d1431da5ec7c0cf4cb Mon Sep 17 00:00:00 2001 From: Jim Carroll Date: Fri, 13 Dec 2024 09:33:50 +1300 Subject: [PATCH] fix: Markdown auto-linting --- content/docs/migrate-from-MKE-3.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/content/docs/migrate-from-MKE-3.md b/content/docs/migrate-from-MKE-3.md index 2b190af7..ecee8ee9 100644 --- a/content/docs/migrate-from-MKE-3.md +++ b/content/docs/migrate-from-MKE-3.md @@ -69,7 +69,7 @@ Verify that you have the following components in place before you begin upgradin keyPath: ``` -- A ``calico_kdd`` flag is set to ``true`` in the MKE 3 configuration +- A `calico_kdd` flag is set to `true` in the MKE 3 configuration file and applied to the MKE 3 cluster: ```yaml @@ -82,12 +82,12 @@ Verify that you have the following components in place before you begin upgradin latest 3.7.x or 3.8.x release. 2. Obtain the MKE 3 configuration file: - + ```shell - $ export MKE_USERNAME= - $ export MKE_PASSWORD= - $ export MKE_HOST= - $ curl --silent --insecure -X GET "https://$MKE_HOST/api/ucp/config-toml" -H "accept: application/toml" -H "Authorization: Bearer $AUTHTOKEN" > mke-config.toml + export MKE_USERNAME= + export MKE_PASSWORD= + export MKE_HOST= + curl --silent --insecure -X GET "https://$MKE_HOST/api/ucp/config-toml" -H "accept: application/toml" -H "Authorization: Bearer $AUTHTOKEN" > mke-config.toml ``` 3. In the `cluster_config` section of the MKE 3 configuration file, set the @@ -318,9 +318,9 @@ parameters between MKE 3 and MKE 4: You can address various potential MKE migration issues using the tips and suggestions detailed herein. -### MKE 3 ``etcdv3`` backend is unsupported for MKE 4 upgrade +### MKE 3 `etcdv3` backend is unsupported for MKE 4 upgrade -During the upgrade from MKE 3 to MKE 4, which defaults to the ``etcdv3`` +During the upgrade from MKE 3 to MKE 4, which defaults to the `etcdv3` backend, you may receive the following error: ```bash @@ -332,7 +332,7 @@ Error: unable to generate upgrade config: unsupported configuration for mke4 upg To resolve the issue, ensure that: - The MKE 3 source is the latest 3.7.x or 3.8.x release. -- The ``calico_kdd`` flag in the MKE 3 configuration file is set to `true`. +- The `calico_kdd` flag in the MKE 3 configuration file is set to `true`. - The configuration is applied to the MKE 3 cluster. {{< callout type="info" >}}