Skip to content

Commit 0cb2730

Browse files
addetzachuribooks
addetz
and
achuribooks
authored
docs: add component update for 2026-06 DOC-2530 PAC-3707 (#9417)
* docs: add component update for 2026-06 DOC-2530 * docs: update packs and add appliance * ci: auto-formatting prettier issues * docs: add known issue * docs: rephrase known issue * docs: add troubleshooting workaround * docs: add update scenario * Apply suggestion from @achuribooks Co-authored-by: Amanda Churi Filanowski <[email protected]> * Apply suggestion from @achuribooks Co-authored-by: Amanda Churi Filanowski <[email protected]> * docs: fix formatting * docs: more updates * docs: reword newer versions --------- Co-authored-by: Amanda Churi Filanowski <[email protected]>
1 parent 3e1c02c commit 0cb2730

File tree

3 files changed

+100
-3
lines changed

3 files changed

+100
-3
lines changed

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,10 @@ The following table lists all known issues that are currently active and affecti
1616

1717
| Description | Workaround | Publish Date | Product Component |
1818
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- |
19-
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2504 --> Existing EKS clusters configured with mismatched Classless Inter-Domain Routing (CIDR) values and NodePool customization using AWS Launch Templates have nodes with incorrect `kubelet` CIDR and `clusterDNS` values. The fix introduced in Palette 4.8.25 applies only to newly created nodes and does not remediate existing nodes. As a result, pods scheduled on the affected nodes may be unable to reach `clusterDNS`. | Restart the pods scheduled on affected nodes so that they are rescheduled onto a healthy node. Normal operation is restored pods are scheduled on nodes with the correct `kubelet` CIDR configurations. | January 30, 2025 | Clusters |
20-
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2490 --> The `spectrocloud_registry_oci` resource or data source continuously detects changes and repeatedly reconciles when created or imported using the Crossplane provider with `is_synchronization` enabled. The Terraform `plan` operation and audit logs also incorrectly report changes. This affects [Spectro Cloud Terraform provider](https://registry.terraform.io/providers/spectrocloud/spectrocloud/latest/docs) and [Spectro Cloud Crossplane provider](https://marketplace.upbound.io/providers/crossplane-contrib/provider-palette) version 0.27.0 or later. | No workaround available. | January 30, 2025 | Terraform, Crossplane |
21-
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2430 --> <!-- prettier-ignore-start --> [Palette Management Appliance](../enterprise-version/install-palette/palette-management-appliance.md) and [VerteX Management Appliance](../vertex/install-palette-vertex/vertex-management-appliance.md) installations may become stuck due to `ErrImagePull` errors on the <VersionedLink text="Calico" url="/integrations/packs/?pack=cni-calico" /> pods. This affects all Palette versions later than 4.8.0. <!-- prettier-ignore-end --> | Restart the node on which the pod is scheduled and wait for the pod to recover. | January 27, 2025 | Clusters, Packs |
19+
| <!-- https://spectrocloud.atlassian.net/browse/PAC-3669 --> Clusters configured with <VersionedLink text="Palette eXtended Kubernetes Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s" /> pack version 1.33.6 and an OIDC provider fail to deploy successfully. | Upgrade to newer Palette eXtended Kubernetes Edge (PXK-E) pack versions. Alternatively, if remaining on PXK-E version 1.33.6, refer to [Scenario - Configure OIDC for Palette eXtended Kubernetes Edge (PXK-E) 1.33.6](../troubleshooting/pack-issues.md#scenario---configure-oidc-for-palette-extended-kubernetes-edge-pxk-e-1336) for the workaround. | February 6, 2026 | Packs, Clusters |
20+
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2504 --> Existing EKS clusters configured with mismatched Classless Inter-Domain Routing (CIDR) values and NodePool customization using AWS Launch Templates have nodes with incorrect `kubelet` CIDR and `clusterDNS` values. The fix introduced in Palette 4.8.25 applies only to newly created nodes and does not remediate existing nodes. As a result, pods scheduled on the affected nodes may be unable to reach `clusterDNS`. | Restart the pods scheduled on affected nodes so that they are rescheduled onto a healthy node. Normal operation is restored pods are scheduled on nodes with the correct `kubelet` CIDR configurations. | January 30, 2026 | Clusters |
21+
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2490 --> The `spectrocloud_registry_oci` resource or data source continuously detects changes and repeatedly reconciles when created or imported using the Crossplane provider with `is_synchronization` enabled. The Terraform `plan` operation and audit logs also incorrectly report changes. This affects [Spectro Cloud Terraform provider](https://registry.terraform.io/providers/spectrocloud/spectrocloud/latest/docs) and [Spectro Cloud Crossplane provider](https://marketplace.upbound.io/providers/crossplane-contrib/provider-palette) version 0.27.0 or later. | No workaround available. | January 30, 2026 | Terraform, Crossplane |
22+
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2430 --> <!-- prettier-ignore-start --> [Palette Management Appliance](../enterprise-version/install-palette/palette-management-appliance.md) and [VerteX Management Appliance](../vertex/install-palette-vertex/vertex-management-appliance.md) installations may become stuck due to `ErrImagePull` errors on the <VersionedLink text="Calico" url="/integrations/packs/?pack=cni-calico" /> pods. This affects all Palette versions later than 4.8.0. <!-- prettier-ignore-end --> | Restart the node on which the pod is scheduled and wait for the pod to recover. | January 27, 2026 | Clusters, Packs |
2223
| <!-- PAC-3584 --> AWS EKS clusters using <VersionedLink text="Kubernetes (EKS)" url="/integrations/packs/?pack=kubernetes-eks" /> version 1.33 with Palette as an Identity Provider (IdP) fail to deploy. This is due to `IdentityProviderConfigName` not being automatically injected into the `values.yaml` file. | In the `managedControlPlane.oidcIdentityProvider` section of your cluster profile's Kubernetes layer, add the value `identityProviderConfigName: "eks-oidc"`. | December 30, 2025 | Packs |
2324
| Velero backups may fail with errors `Timed out awaiting reconciliation of volumesnapshot hipster-app/velero-data-redis-cart-2-zctck`. This occurs because the CloudStack CSI Helm chart is missing the required csi-snapshotter sidecar container in the controller deployment, preventing CSI snapshot operations from executing. As a result, all CSI-based snapshots and any Velero backups that rely on them time out and fail. | No workaround available. | December 17, 2025 | Packs |
2425
| Edge hosts using encrypted persistent partitions may fail to complete a reset. A limitation in Kairos version 3.5.3 prevents these partitions from being reinitialized during the reset workflow, resulting in the operation stopping prematurely. | Refer to [Troubleshooting - Edge](../troubleshooting/edge/edge.md#scenario---edge-host-reset-fails-with-encrypted-persistent-partition) for the workaround. | December 17, 2025 | Edge |

0 commit comments

Comments
 (0)