You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Palette Extended Kubernetes - Edge (PXK-E) version 1.31 is not yet supported for Edge clusters. | No workaround is available. | February 24, 2025 | Edge |
20
-
| K3s certificate renewals for [Two-node Edge clusters](../clusters/edge/architecture/two-node.md) are not managed by Palette. Two-node clusters will use a default certificate list. | No workaround available. Refer to [k3s certificate](https://docs.k3s.io/cli/certificate) for manual guidance. | February 17, 2025 | Edge |
21
20
| [MAAS](../clusters/data-center/maas/maas.md) and [VMware vSphere](../clusters/data-center/vmware/vmware.md) clusters fail to provision on existing self-hosted Palette and VerteX environments deployed with Palette 4.2.13 or later. These installations have an incorrectly configured default image endpoint, which causes image resolution to fail. New self-hosted installations are not affected. | Refer to [Troubleshooting](../troubleshooting/enterprise-install.md#scenario---maas-and-vmware-vsphere-clusters-fail-image-resolution-in-non-airgap-environments) for a workaround for non-airgap environments. For airgap environments, ensure that the images are downloaded to your environment. Refer to the [Additional OVAs](../enterprise-version/install-palette/airgap/supplemental-packs.md#additional-ovas) section for further details. | February 16, 2025 | Self-Hosted, Clusters |
22
21
| [Cluster Removal](../clusters/cluster-management/remove-clusters.md) of Palette and VerteX clusters will get stuck if you attempt to delete a cluster with expired cloud account credentials. This may lead to cloud resources not being correctly removed incurring unexpected cloud costs. | Ensure that the cloud account credentials registered to your cluster are not expired. You can update your cloud accounts from **Tenant Settings** > **Cloud Accounts**. If your cluster is stuck in the **Deleting** state for more than 15 minutes, you can [force delete the cluster](../clusters/cluster-management/remove-clusters.md#force-delete-a-cluster). You can then manually remove all Palette-provisioned resources associated with the cluster. | February 16, 2025 | Clusters |
23
22
| Performing a [MicroK8s](../integrations/kubernetes-microk8s.md) `InPlaceUpgrade` from version 1.28 to 1.29 on active MAAS and AWS clusters with Cilium prevents new pods from being deployed on control plane nodes due to an [upstream issue](https://github.com/canonical/cluster-api-control-plane-provider-microk8s/issues/74) with Canonical. This issue also occurs when performing a MicroK8s `SmartUpgrade` from version 1.28 to 1.29 on active MAAS and AWS clusters with one control plane node and Cilium. | Manually restart the Cilium pods on _each_ control plane node using the command `microk8s kubectl rollout restart daemonset cilium --namespace kube-system`. | February 16, 2025 | Clusters, Packs |
@@ -101,6 +100,7 @@ for information on the fix version and the date the issue was resolved.
101
100
102
101
| Description | Publish Date | Product Component | Fix Version |
| K3s certificate renewals for [Two-node Edge clusters](../clusters/edge/architecture/two-node.md) are not managed by Palette. Two-node clusters will use a default certificate list. | February 17, 2025 | Edge | 4.6.8 |
104
104
| 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 and the resize of control plane nodes for clusters using 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. | January 19, 2025 | Clusters, Packs | 4.6.0 |
105
105
| Deployed clusters using a Palette version before 4.4.20 will not have accurate Kubernetes certificate expiration information displayed on the Palette UI certificate page. Starting with Palette version 4.4.20, the certificate information displayed on the certificate management page will be correct. | October 31, 2024 | Clusters | 4.4.20 |
106
106
| A change in the [Edge Cluster](https://docs.spectrocloud.com/api/v1/v-1-spectro-clusters-edge-native-create/) API endpoint affects Terraform and API workflows for Edge cluster creation or modification. The field `spec.cloudConfig.controlPlaneEndpoint.type` no longer accepts IP addresses. The accepted values are now `VIP`, `External`, and `DDNS`. As a result, API and Terraform workflows for Edge cluster creation or modification that use the IP address are currently unavailable. | September 18, 2024 | Edge | 4.4.19 |
0 commit comments