Skip to content

Commit 3dd5253

Browse files
svetlana-efimovaSvetlana Efimovacaroldelwing
authored
docs: Add agent/k8s packs known issue (#7918)
* Add agent/k8s packs known issue * An empty commit to trigger the Netlify preview * ci: auto-formatting prettier issues * Update docs/docs-content/release-notes/known-issues.md Co-authored-by: caroldelwing <[email protected]> * ci: auto-formatting prettier issues --------- Co-authored-by: Svetlana Efimova <[email protected]> Co-authored-by: svetlana-efimova <[email protected]> Co-authored-by: caroldelwing <[email protected]>
1 parent 55e0e92 commit 3dd5253

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

‎docs/docs-content/release-notes/known-issues.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ The following table lists all known issues that are currently active and affecti
1616

1717
| Description | Workaround | Publish Date | Product Component |
1818
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- |
19+
| Edge clusters with the Palette agent versions prior to 4.7.b do not support upgrading to the following Kubernetes pack versions released in 4.7.b: <VersionedLink text="Palette Optimized Canonical" url="/integrations/packs/?pack=edge-canonical" /> 1.32.8 and 1.33.4; <VersionedLink text="Palette eXtended Kubernetes Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s" /> 1.31.12, 1.32.8, and 1.33.4. This issue affects agent mode clusters only and does not impact appliance mode clusters. | For locally managed clusters, refer to [Configure Palette Agent Version](../clusters/edge/cluster-management/agent-upgrade-airgap.md) to upgrade the agent to the latest version before upgrading Kubernetes packs. For centrally managed clusters, do not [pause upgrades](../clusters/cluster-management/platform-settings/pause-platform-upgrades.md) so the agent can upgrade automatically. | September 13, 2025 | Edge, Packs |
1920
| In self-hosted [Palette](../enterprise-version/install-palette/palette-management-appliance.md) and [Vertex Management Appliance](../vertex/install-palette-vertex/vertex-management-appliance.md) environments, uploading the same pack as both a FIPS and non-FIPS version to the same registry overwrites the original pack.<br /><br /> For example, if you have a non-FIPS version of the `byoi-2.1.0` pack in your Zot registry and you upload the FIPS version of `byoi-2.1.0`, the new version will overwrite the existing one. This results in a SHA mismatch between the pack stored in the registry and the pack referenced in the cluster profile, which can lead to cluster creation failures. | Upload either a FIPS or non-FIPS version of a pack to your registry. Do not upload both to the same registry. | August 18, 2025 | Clusters, Self-Hosted |
2021
| Cilium may fail to start on MAAS machines that are configured with a `br0` interface and are part of a <VersionedLink text="Canonical Kubernetes" url="/integrations/packs/?pack=kubernetes-ck8s" /> cluster, displaying errors like `daemon creation failed: failed to detect devices: unable to determine direct routing device. Use --direct-routing-device to specify it`. This happens because Canonical Kubernetes supports setting various Cilium annotations, but it lacks some fields required for the MAAS `br0` network configuration due to [a limitation in `k8s-snap`](https://github.com/canonical/k8s-snap/issues/1740). | Avoid using MAAS machines with a `br0` interface when provisioning Canonical Kubernetes clusters. Instead, choose machines whose primary interface is directly connected to the MAAS-managed subnet or VLAN. | August 17, 2025 | Clusters, Packs |
2122
| Container runtime may fail to run with the message `Failed to run CRI service error=failed to recover state: failed to get metadata for stored sandbox` after a node is upgraded to 1.29.14. This is related to an [upstream issue with containerd](https://github.com/containerd/containerd/issues/10848). | Remove the container runtime folder with `rm -rf /var/lib/containerd`. Then restart containerd and kubelet using `systemctl restart containerd && systemctl restart kublet`. | August 17, 2025 | Edge |

0 commit comments

Comments
 (0)