From e1cafd64ca4390518ff083f0775aee2fe9ae98eb Mon Sep 17 00:00:00 2001 From: KoryKessel-Mirantis Date: Thu, 6 Jun 2024 20:09:31 +0200 Subject: [PATCH 1/3] Creation of Known Issues topic --- content/docs/reference/known-issues.md | 61 ++++++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 content/docs/reference/known-issues.md diff --git a/content/docs/reference/known-issues.md b/content/docs/reference/known-issues.md new file mode 100644 index 00000000..1283b095 --- /dev/null +++ b/content/docs/reference/known-issues.md @@ -0,0 +1,61 @@ +# Known issues + +Workaround solutions are available for the following MKE 4 Alpha.1 known +issues: + +## [BOP-694] MKE 3 upgrade rollback destabilizes the cluster + +When a rollback to MKE 3 occurs as the result of an upgrade issue, the MKE +cluster is inaccessible through the MKE web UI address and ``ucp-auth`` +containers continually restart. + +**Workaround:** Uninstall MKE 3 and restore it from a backup. + +## [BOP-708] RBAC resource creation fails during mkectl upgrade when OIDC enabled + +During a mkectl upgrade from MKE 3, RBAC resource creation fails when OIDC is +enabled. + +**Workaround:** + +1. Copy the MKE 4 config that prints at the end of migration. + + Example: + + ``` + INF Below is your new MKE 4 config. Save it to a file and use it to configure the MKE 4 cluster with mkectl apply: + ``` + +2. Update the ``authentication.oidc.clientSecret`` field to the secret field + from your identity provider. + +3. Apply the updated MKE 4 config. + +## [BOP-686] In MKE 3 upgrade, kubectl commands return ``No agent available`` + +For a cluster with multiple controller nodes (manager/master nodes), [k0s +requires the presence ofa load balancer for the controller +node](https://docs.k0sproject.io/head/high-availability/ ). Without a load +balancer, the controller nodes is unable to reach the kubelet on the worker +nodes, and thus the user will be presented with ``No agent available`` errors. + +**Workaround:** + +1. If an external load balancer is not already in place, create one that + targets all controllers and that forwards the following ports: + + - `443`, for controller + - `6443`, for Kubernetes API + - `8132`, for Konnectivity + +2. Use `k0sctl` to update the `k0s` config to set `externalAddress`: + + ``` + k0s: + config: + spec: + api: + externalAddress: + sans: + - + ``` From 6bf7d9713adf49b3308e933518d6ba7fd978d75a Mon Sep 17 00:00:00 2001 From: KoryKessel-Mirantis Date: Fri, 7 Jun 2024 00:19:46 +0200 Subject: [PATCH 2/3] Edits in response to review of [BOP-708] known issue content. --- content/docs/reference/known-issues.md | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/content/docs/reference/known-issues.md b/content/docs/reference/known-issues.md index 1283b095..a8734d6d 100644 --- a/content/docs/reference/known-issues.md +++ b/content/docs/reference/known-issues.md @@ -11,21 +11,15 @@ containers continually restart. **Workaround:** Uninstall MKE 3 and restore it from a backup. -## [BOP-708] RBAC resource creation fails during mkectl upgrade when OIDC enabled +## [BOP-708] OIDC authenticaion fails after mkectl upgrade -During a mkectl upgrade from MKE 3, RBAC resource creation fails when OIDC is -enabled. +Due to an issue with client secret migration, OIDC authentication fails +following an upgrade performed with mkectl. **Workaround:** 1. Copy the MKE 4 config that prints at the end of migration. - Example: - - ``` - INF Below is your new MKE 4 config. Save it to a file and use it to configure the MKE 4 cluster with mkectl apply: - ``` - 2. Update the ``authentication.oidc.clientSecret`` field to the secret field from your identity provider. From 5936e5086fb245e03d129e9c25ed447643ce8128 Mon Sep 17 00:00:00 2001 From: KoryKessel-Mirantis Date: Fri, 7 Jun 2024 21:48:14 +0200 Subject: [PATCH 3/3] Edits in reference to SME review comments from RyanZ and Ranyodh. --- content/docs/{reference => }/known-issues.md | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) rename content/docs/{reference => }/known-issues.md (78%) diff --git a/content/docs/reference/known-issues.md b/content/docs/known-issues.md similarity index 78% rename from content/docs/reference/known-issues.md rename to content/docs/known-issues.md index a8734d6d..3e49a47f 100644 --- a/content/docs/reference/known-issues.md +++ b/content/docs/known-issues.md @@ -1,16 +1,8 @@ # Known issues -Workaround solutions are available for the following MKE 4 Alpha.1 known +Workaround solutions are available for the following MKE 4.0.0-alpha.1.0 known issues: -## [BOP-694] MKE 3 upgrade rollback destabilizes the cluster - -When a rollback to MKE 3 occurs as the result of an upgrade issue, the MKE -cluster is inaccessible through the MKE web UI address and ``ucp-auth`` -containers continually restart. - -**Workaround:** Uninstall MKE 3 and restore it from a backup. - ## [BOP-708] OIDC authenticaion fails after mkectl upgrade Due to an issue with client secret migration, OIDC authentication fails