diff --git a/docs/docs-content/clusters/edge/cluster-management/skip-draining.md b/docs/docs-content/clusters/edge/cluster-management/skip-draining.md index 91579a5d75..880f2d088c 100644 --- a/docs/docs-content/clusters/edge/cluster-management/skip-draining.md +++ b/docs/docs-content/clusters/edge/cluster-management/skip-draining.md @@ -79,5 +79,5 @@ will apply to both appliance mode and [agent mode](../../../deployment-modes/age [Edge Cluster Upgrade Behavior](../cluster-management/upgrade-behavior.md). 2. After the upgrade is completed, use `kubectl logs` to check on a node for which you skipped pod draining. Confirm - that no messages that look like `Evicting pod as part of upgrade plan` are displayed. The absence of - such messages means that the pods were not drained during the upgrade. + that no messages that look like `Evicting pod as part of upgrade plan` are displayed. The absence of such + messages means that the pods were not drained during the upgrade. diff --git a/docs/docs-content/release-notes/known-issues.md b/docs/docs-content/release-notes/known-issues.md index ae4aaf487b..7e4d97aef7 100644 --- a/docs/docs-content/release-notes/known-issues.md +++ b/docs/docs-content/release-notes/known-issues.md @@ -16,6 +16,8 @@ The following table lists all known issues that are currently active and affecti | Description | Workaround | Publish Date | Product Component | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- | +| Hosts provisioned in [agent mode](../deployment-modes/agent-mode/agent-mode.md) do not display host information in the console after using the Palette Terminal User Interface to complete host setup. | Local UI is still available and will display host information. Refer to [Access Local UI](../clusters/edge/local-ui/host-management/access-console.md) to learn how to access Local UI. | December 12, 2024 | Edge | +| In a multi-node Edge cluster, the reset action on a cluster node does not update the node status on the leader node's linking screen. | [Scale down](../clusters/edge/local-ui/cluster-management/scale-cluster.md#scale-down-a-cluster) the cluster and free up the follower node before resetting the node. | December 12, 2024 | Edge | | For Edge airgap clusters, manifests attached to packs are not applied during cluster deployment. | Add the manifest as a layer directly instead of attaching it to a pack. For more information, refer to [Add a Manifest](../profiles/cluster-profiles/create-cluster-profiles/create-addon-profile/create-manifest-addon.md). | November 15, 2024 | Edge | | In some cases, the differential editor incorrectly reports YAML differences for customizations not created by you. The issue is more common when items in a list or array are removed. Clicking the **Keep** button when non-user-generated customization is the focus causes the button to become unresponsive after the first usage. | Skip differential highlights not created by you. Click the arrow button to skip and proceed. | November 11, 2024 | Cluster Profiles | | Palette fails to provision virtual clusters on airgapped and proxy Edge cluster groups. This error is caused by Palette incorrectly defaulting to fetch charts from an external repository, which is unreachable from these environments. | No workaround. | November 9, 2024 | Virtual Clusters |