From cc8fc200ab4f6f9d7a8dcad3ad72d47f054e9bc2 Mon Sep 17 00:00:00 2001 From: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> Date: Thu, 23 Jan 2025 14:52:49 -0700 Subject: [PATCH] docs: DOC-1617 (#5554) * docs: DOC-1617 * docs: addition * docs: apply suggestions from code review Co-authored-by: Ben Radstone <56587332+benradstone@users.noreply.github.com> * chore: updated message * chore: vale feedback * docs: apply suggestions from code review Co-authored-by: Amanda Churi Filanowski * ci: auto-formatting prettier issues --------- Co-authored-by: Ben Radstone <56587332+benradstone@users.noreply.github.com> Co-authored-by: Amanda Churi Filanowski --- docs/docs-content/release-notes/known-issues.md | 1 + docs/docs-content/release-notes/release-notes.md | 10 ++++++++++ 2 files changed, 11 insertions(+) diff --git a/docs/docs-content/release-notes/known-issues.md b/docs/docs-content/release-notes/known-issues.md index 2c003ba4f8..a709d723dc 100644 --- a/docs/docs-content/release-notes/known-issues.md +++ b/docs/docs-content/release-notes/known-issues.md @@ -16,6 +16,7 @@ The following table lists all known issues that are currently active and affecti | Description | Workaround | Publish Date | Product Component | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- | +| Clusters that are currently deployed and attempting to upgrade from Kubernetes version 1.31.1 to newer versions are getting stuck in the upgrade state. This issue also affects Day-2 operations related to changes in the Kubernetes layer YAML for clusters on Kubernetes version 1.31.1. The root of the problem is an internal conversion error stemming from an internal type change introduced in Kubernetes version 1.31.x. | Avoid upgrading Kubernetes clusters from version 1.31.1 or modifying the Kubernetes YAML as a Day-2 operation on clusters with Kubernetes 1.31.1. You can deploy new clusters using version 1.31.4, as new deployments are unaffected by the issue. If you upgraded and the cluster remains stuck, revert the change and downgrade to version 1.31.1. | January 19, 2025 | Clusters, Packs | | For clusters deployed with [agent mode](../deployment-modes/agent-mode/agent-mode.md) on Palette agent version 4.5.14, having a custom `stylus.path` defined in the **user-data** file causes Kubernetes upgrades to fail. This affects all Kubernetes packs. | No workaround available. Refer to [Identify the Target Agent Version](../clusters/edge/cluster-management/agent-upgrade-airgap.md#identify-the-target-agent-version) for guidance in retrieving your Palette agent version number. | January 19, 2025 | Edge | | For clusters deployed with and [agent mode](../deployment-modes/agent-mode/agent-mode.md) on Palette agent version 4.5.14, adding a custom `stylus.path` to the **user-data** file causes cluster creation to fail as it cannot find [kubeadm](https://kubernetes.io/docs/reference/setup-tools/kubeadm/). | Review the [Edge Troubleshooting](../troubleshooting/edge.md) section for workarounds. Refer to [Identify the Target Agent Version](../clusters/edge/cluster-management/agent-upgrade-airgap.md#identify-the-target-agent-version) for guidance in retrieving your Palette agent version number. | January 19, 2025 | Edge | | For clusters deployed with and [agent mode](../deployment-modes/agent-mode/agent-mode.md), upgrades to higher Kubernetes versions are not supported with Palette agent version 4.5.12 or earlier. | No workaround available. Upgrades to higher Kubernetes versions are only supported from Palette agent version 4.5.14 and above for clusters deployed with PXK-E and agent mode. Refer to [Identify the Target Agent Version](../clusters/edge/cluster-management/agent-upgrade-airgap.md#identify-the-target-agent-version) for guidance in retrieving your Palette agent version number. | January 19, 2025 | Edge | diff --git a/docs/docs-content/release-notes/release-notes.md b/docs/docs-content/release-notes/release-notes.md index 540e14eb72..20ca600f06 100644 --- a/docs/docs-content/release-notes/release-notes.md +++ b/docs/docs-content/release-notes/release-notes.md @@ -78,6 +78,16 @@ about the rolling upgrade strategy. [Image Pull Secret](../enterprise-version/install-palette/install-on-kubernetes/palette-helm-ref.md#image-pull-secret) section of the Palette Helm Chart documentation to learn more about using custom image pull secrets. +#### Known Issues + +- Clusters that are currently deployed and attempting to upgrade from Kubernetes version 1.31.1 to newer versions are + getting stuck in the upgrade state. This issue also affects Day-2 operations related to changes in the Kubernetes + layer YAML for clusters on Kubernetes version 1.31.1. The root of the problem is an internal conversion error stemming + from a change introduced in Kubernetes version 1.31.x. clusters from version 1.31.1 or modifying the Kubernetes YAML + as a Day-2 operation on clusters with Kubernetes 1.31.1. You can deploy new clusters using version 1.31.4, as new + deployments are unaffected by the issue. If you upgraded and the cluster remains stuck, revert the change and + downgrade to version 1.31.1. + ### Edge #### Features