Skip to main content

Announcements

This page lists the upcoming breaking changes, deprecations, and removals in Palette and Palette VerteX.

Upcoming Breaking Changes​

tip

Use the Find Breaking Changes page to list all the breaking changes between Palette versions.

Stay informed about the upcoming breaking changes in Palette and Palette VerteX. Use the information below to prepare for the changes in your environment.

ChangeTarget DatePublished Date
In an upcoming 4.10 release, workload clusters transition to security-hardened images for Palette SaaS, self-hosted Palette, and Palette VerteX. Verify that your workload clusters use containerd 2.0 or later and Palette agent version 4.9.23 or later. Otherwise, the transition might affect both existing and new clusters. Refer to Prepare Clusters for Security-Hardened Images for the supported Kubernetes versions and the steps to meet each requirement.To be announcedOctober 9, 2026
Spectro Cloud is transitioning to the use of security-hardened images. As a result, retrieving images from Spectro Cloud OCI registries will now require a Spectro Cloud image pull secret. This secret is intended for long-term use and is configured once. Image pulls from Spectro Cloud registries will not be allowed unless a valid image pull secret is configured.

This change primarily affects non-airgap environments that do not configure mirror registries or image swap; it does not apply to airgapped environments, which pull images from their own registries. To obtain your image pull secret, contact your Spectro Cloud customer support representative. Refer to Configure Image Pull Secret for more information.
To be announcedJune 28, 2026
AWS GovCloud and Azure Government cloud, currently disabled in the Palette UI, will be removed from the Palette API, Spectro Cloud Terraform provider, and Spectro Cloud Crossplane provider in an upcoming release. To continue deploying and managing clusters using AWS GovCloud or Azure Government cloud, use Palette VerteX instead.To be announcedMay 3, 2026

Deprecations​

The table below lists the upcoming deprecations in Palette and Palette VerteX. Review the information to below and take necessary actions to avoid any disruptions in your environment.

ChangeTarget Removal DatePublished Date
The Quickstart OVA installer for Palette is now deprecated. The Quickstart OVA was introduced in the Palette 3.x series to deploy a single-node Palette instance on VMware vSphere and was replaced in Palette 4.0 by the EC command of the Palette CLI. If you have already migrated to an Enterprise Cluster installation, no action is required. If your Palette installation was deployed in quick start mode, migrate to Enterprise Cluster by following the process outlined in the legacy Palette 3.x installation guide.November 29, 2026July 30, 2026
The /clusterprofiles API endpoint is now deprecated. Use the /dashboard/clusterprofiles endpoint instead, which includes improved data retrieval capabilities.November 15, 2026May 3, 2026
Support for Red Hat Enterprise Linux (RHEL) 8.x in Edge workflows has been deprecated, including FIPS-enabled configurations. We recommend using RHEL 9.x or RHEL 10.x.To be announcedMay 3, 2026
Support for Ubuntu 20.04 in Edge workflows has been deprecated, including FIPS-enabled configurations. We recommend using Ubuntu 24.04, as it is FIPS 140-3 compliant.To be announcedMay 3, 2026
The /kubeconfig API endpoint has now been deprecated. Use the /kubeconfigclient or /adminKubeconfig API endpoint to download kubeconfig files instead. Refer to our Kubeconfig guide for more information on the types of cluster kubeconfig files.November 29, 2026April 5, 2026
The Spectro Kubernetes Dashboard and Kubernetes Dashboard packs are deprecated and have now moved to the Disabled stage. This is due to the archiving of upstream projects. These packs are no longer available for selection when you create a cluster profile, but you can still launch new clusters from existing cluster profiles that contain either pack. Refer to Pack Deprecations for a description of each deprecation stage. November 14, 2026January 18, 2026
The Nginx pack is deprecated and has now moved to the Disabled stage. The pack is no longer available for selection when you create a cluster profile, but you can still launch new clusters from existing cluster profiles that contain it. We recommend using an alternative ingress controller, such as Kgateway or Traefik. Refer to the Ingress NGINX Retirement: What You Need to Know blog for further information, and to Pack Deprecations for a description of each deprecation stage. December 4, 2026November 22, 2025

Removals​

You can review the deprecations that have been removed in Palette and VerteX in the following table. Refer to respective release version's Release Notes for more information.

ChangeReleaseDate
The MicroK8s pack is no longer available in Palette and Palette VerteX. Use Canonical Kubernetes (CK8s) instead.4.10.25October 9, 2026
K3s is no longer a supported distribution for Palette and Palette VerteX virtual clusters or cluster groups. Palette upgraded vCluster to 0.36.x, and upstream vCluster removed K3s in 0.33. Existing K3s virtual clusters continue to run on their current vCluster version. To move to a newer vCluster version, create a new Kubernetes-based cluster group and migrate your workloads.4.10.25October 9, 2026
EKS Hybrid Nodes are no longer available in Palette and Palette VerteX. Hybrid node configuration controls are disabled in the Palette UI on imported EKS clusters, and API requests that enable or configure hybrid nodes are rejected. Existing clusters with hybrid nodes continue to operate, but you cannot add or modify hybrid configuration. Deploy your workloads to EKS clusters instead.4.10.25October 9, 2026
The GET /v1/projects Palette API endpoint is no longer available. Use the POST /v1/dashboard/projects endpoint instead, which supports the filtering and sorting that the removed endpoint lacked.4.10.13September 6, 2026
The internal Ingress Nginx controller used by Palette and Palette VerteX management plane services has been removed. Traefik is now the sole management cluster ingress controller. Most cleanup is automatic. The management plane removes leftover Nginx resources at startup. Refer to the Upgrade Palette on Kubernetes guide for the pre-upgrade GKE Identity and Access Management (IAM) requirements and recommended values.yaml hygiene.4.9.14May 31, 2026
The Palette Edge CLI is deprecated and there will be no more releases. We recommend using the Palette CLI for the creation and management of content bundles. Refer to the Build Content Bundle guide for further information.4.9.14May 31, 2026
EKS-optimized Amazon Linux 2 (AL2) AMIs are now disabled. For new clusters, you are no longer able to select the AL2 AMIs for EKS worker nodes in Palette. For existing clusters, you must create new worker nodes using AL2023 AMIs. Existing AL2 AMI worker nodes will no longer receive bug fixes or security patches. Refer to our Scenario - Unable to Upgrade EKS Worker Nodes from AL2 to AL2023 guide for help with migrating workloads.4.9.5May 3, 2026
OpenStack is no longer supported in Palette. We recommend migrating your workloads to another supported data center environment.4.8.47April 5, 2026
The stylus.installationMode Edge Installer Configuration flag is no longer available. Use the stylus.managementMode flag instead, which has two allowed values: central, which means the Edge host is connected to Palette, and local, which means the Edge host has no connection to a Palette instance. Refer to the Prepare User Data guide for further information.4.8.21January 18, 2026
The stylus.includeTui Edge Installer Configuration flag is no longer supported. The TUI is always enabled regardless of its value. To prevent users from modifying Edge host and network settings through the TUI, use the stylus.disableTui flag.4.8.6November 22, 2025
The spec.jsonCredentialsFileUid field in API requests is no longer available. Users who create GCP cloud accounts using the API should use the spec.jsonCredentials field to supply their credentials in JSON format. Refer to the API documentation for further details.4.7.20September 13, 2025
The spectrocloud_macro Terraform resource is no longer available. We recommend using the spectrocloud_macros resource to create and manage service output variables and macros. For more information, refer to the Spectro Cloud Terraform provider documentation.4.7.20September 13, 2025
The tc subcommand of the Palette CLI is no longer available. This command provided functionality for deploying target clusters using the Palette CLI. We recommend using the Spectro Cloud Terraform provider for cluster deployment automation.4.7.13August 17, 2025
The PROXY_CERT_PATH variable is no longer available in the CanvOS build process. Use the certs folder in the root of the project directory to store proxy certificates. The certs folder is automatically included in the CanvOS build process. Refer to the Build Provider Images for guidance on using the certs folder to pass proxy certificates to the CanvOS build process.4.6.12March 15, 2025
Palette's internal message communication between components transitioned from NATS to gRPC. The previous usage of NATS has been removed. This change primarily affects customers using Palette agents on versions older than 4.0. If your clusters still use agents on version 3.x or older, resume agent upgrades to avoid disrupting critical functions such as health monitoring and heartbeat publishing. To learn more about Palette's internal network architecture, refer to the Network Ports page. If you are using network proxies, we recommend you review the gRPC and Proxies documentation for potential issues.4.6.12March 15, 2025
The Palette CLI now requires an encryption passphrase for various commands. The passphrase can be set as an environment variable or using a CLI command flag. The passphrase encrypts and decrypts sensitive data, such as secrets, in the CLI configuration files. Refer to the Palette CLI Encryption section to learn more about the encryption passphrase.4.5.20January 18, 2024
The Terraform resource, spectrocloud_cluster_import is removed. To import a cluster deployed outside of the context of Palette, refer to the Import a Cluster guide.4.5.20January 18, 2024
Due to Google's decision to deprecate the gcr.io container registry, we are adding a new image registry that Palette agents will use to pull images. The new registry is us-docker.pkg.dev. If you have network restrictions in place, ensure that the new registry is allowed. Ensure network connections to grc.io are allowed until the migration is complete. The new registry is available for use starting with this release. Refer to the Proxy Requirements for a complete list of domains that must be allowed.4.5.3October 13, 2024
In this release, Palette aligns Google Cloud Platform GKE behavior with Azure AKS and AWS EKS and removes the ability to specify a patch version when creating a cluster profile for AKS, EKS, and GKE. Only the major and minor versions are available for selection. The underlying cloud provider will automatically select the latest patch version available for the selected major and minor version.4.4.6Jun 15, 2024