docs: add release notes DOC-1663 #5692
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
addetz
force-pushed
the
doc-1663-release-notes-4-6
branch
from
e55ee9c to
8fad759
Compare
✅ Deploy Preview for docs-spectrocloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
🤖 Netlify configured to enable preview build for branch: doc-1663-release-notes-4-6 . Subsequent commits will automatically trigger a Netlify build preview. |
achuribooks
approved these changes
Feb 7, 2025
Co-authored-by: Amanda Churi Filanowski <[email protected]>
addetz
force-pushed
the
doc-1663-release-notes-4-6
branch
from
56a86f6 to
49b71a8
Compare
caroldelwing
approved these changes
Feb 7, 2025
| | The EdgeForge build process utility, CanvOS has an argument variable named `PROXY_CERT_PATH`. This variable is deprecated and no longer the recommended way to pass proxy certificates to 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](../clusters/edge/edgeforge-workflow/palette-canvos/build-provider-images.md) for guidance on using the **certs** folder to pass proxy certificates to the CanvOS build process. | March 15, 2025 | December 7, 2024 | | ||
| | Change | Target Date | Published Date | | ||
| | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ------------------ | | ||
| | The EdgeForge build process utility, CanvOS has an argument variable named `PROXY_CERT_PATH`. This variable is deprecated and no longer the recommended way to pass proxy certificates to 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](../clusters/edge/edgeforge-workflow/palette-canvos/build-provider-images.md) for guidance on using the **certs** folder to pass proxy certificates to the CanvOS build process. | March 15, 2025 | December 7, 2024 | |
There was a problem hiding this comment.
Suggested change
| | The EdgeForge build process utility, CanvOS has an argument variable named `PROXY_CERT_PATH`. This variable is deprecated and no longer the recommended way to pass proxy certificates to 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](../clusters/edge/edgeforge-workflow/palette-canvos/build-provider-images.md) for guidance on using the **certs** folder to pass proxy certificates to the CanvOS build process. | March 15, 2025 | December 7, 2024 | | |
| | The EdgeForge build process utility, CanvOS, has an argument variable named `PROXY_CERT_PATH`. This variable is deprecated and no longer the recommended way to pass proxy certificates to 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](../clusters/edge/edgeforge-workflow/palette-canvos/build-provider-images.md) for guidance on using the **certs** folder to pass proxy certificates to the CanvOS build process. | March 15, 2025 | December 7, 2024 | |
| | Change | Target Date | Published Date | | ||
| | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ------------------ | | ||
| | The EdgeForge build process utility, CanvOS has an argument variable named `PROXY_CERT_PATH`. This variable is deprecated and no longer the recommended way to pass proxy certificates to 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](../clusters/edge/edgeforge-workflow/palette-canvos/build-provider-images.md) for guidance on using the **certs** folder to pass proxy certificates to the CanvOS build process. | March 15, 2025 | December 7, 2024 | | ||
| | Palette's internal message communication between components transitioned from NATS to gRPC. The previous usage of NATS has been deprecated and will be removed in a future release. This change primarily affects customers using Palette agents on versions older than 4.0. If your tenant clusters still use agents on version 3.x or older, [resume agent upgrades](../clusters/cluster-management/platform-settings/pause-platform-upgrades.md) 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](../architecture/networking-ports.md) page. If you are using network proxies, we recommend you review the [gRPC and Proxies](../architecture/grps-proxy.md) documentation for potential issues. | March 15, 2025 | September 14, 2024 | |
There was a problem hiding this comment.
Suggested change
| | Palette's internal message communication between components transitioned from NATS to gRPC. The previous usage of NATS has been deprecated and will be removed in a future release. This change primarily affects customers using Palette agents on versions older than 4.0. If your tenant clusters still use agents on version 3.x or older, [resume agent upgrades](../clusters/cluster-management/platform-settings/pause-platform-upgrades.md) 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](../architecture/networking-ports.md) page. If you are using network proxies, we recommend you review the [gRPC and Proxies](../architecture/grps-proxy.md) documentation for potential issues. | March 15, 2025 | September 14, 2024 | | |
| | Palette's internal message communication between components transitioned from NATS to gRPC. The previous usage of NATS has been deprecated and will be removed in a future release. 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](../clusters/cluster-management/platform-settings/pause-platform-upgrades.md) 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](../architecture/networking-ports.md) page. If you are using network proxies, we recommend you review the [gRPC and Proxies](../architecture/grps-proxy.md) documentation for potential issues. | March 15, 2025 | September 14, 2024 | |
only tenant clusters or all clusters? :)
|
|
||
| - [Self-hosted Palette](../enterprise-version/enterprise-version.md) and Dedicated Palette SaaS installations now offer | ||
| complete brand customization. System operators can apply custom logos and color schemes to the instances they manage | ||
| by using the **Customize interface** tab in the **Administration** panel in the system control. Refer to the Customize |
There was a problem hiding this comment.
Suggested change
| by using the **Customize interface** tab in the **Administration** panel in the system control. Refer to the Customize | |
| by using the **Customize interface** tab in the **Administration** panel of the system console. Refer to the Customize |
maybe?
Comment on lines
+55
to
+58
| - <TpBadge /> Palette now supports a two node architecture, which provides High Availability (HA) mode. Users can access | ||
| this feature by using a toggle to enable high availability mode during cluster configuration. High availability mode | ||
| replaces etcd with Postgres and [Kine](https://github.com/k3s-io/kine). Refer to the Two Node Architecture page for | ||
| further details. |
There was a problem hiding this comment.
Suggested change
| - <TpBadge /> Palette now supports a two node architecture, which provides High Availability (HA) mode. Users can access | |
| this feature by using a toggle to enable high availability mode during cluster configuration. High availability mode | |
| replaces etcd with Postgres and [Kine](https://github.com/k3s-io/kine). Refer to the Two Node Architecture page for | |
| further details. | |
| - <TpBadge /> Palette now supports a two node architecture, which provides a High Availability (HA) mode. Users can enable this feature by toggling the high availability mode during cluster configuration. In HA mode, etcd is replaced with Postgres and [Kine](https://github.com/k3s-io/kine). Refer to the Two Node Architecture page for | |
| further details. |
maybe? also, are we using two node or two-node?
|
|
||
| #### CSI | ||
| - Palette support for <VersionedLink text="MicroK8s" url="/integrations/packs/?pack=kubernetes-microk8s" /> 1.29 and 1.30 has been enhanced to provide airgap support, as well as deployments on [MAAS](../clusters/data-center/maas/maas.md) and [AWS](../clusters/public-cloud/aws/aws.md). Additionally, this update validates multi-node control planes. |
There was a problem hiding this comment.
Suggested change
| - Palette support for <VersionedLink text="MicroK8s" url="/integrations/packs/?pack=kubernetes-microk8s" /> 1.29 and 1.30 has been enhanced to provide airgap support, as well as deployments on [MAAS](../clusters/data-center/maas/maas.md) and [AWS](../clusters/public-cloud/aws/aws.md). Additionally, this update validates multi-node control planes. | |
| - Palette's support for <VersionedLink text="MicroK8s" url="/integrations/packs/?pack=kubernetes-microk8s" /> 1.29 and 1.30 has been enhanced to provide airgap support, as well as deployments on [MAAS](../clusters/data-center/maas/maas.md) and [AWS](../clusters/public-cloud/aws/aws.md). Additionally, this update validates multi-node control planes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the Change
This PR adds the release notes to the release branch. It also adds the NATS removal to the announcements page. This was originally posted in 4.4 release notes as a breaking change but was missed on the announcements page.
Changed Pages
💻 Release Notes
💻 Announcements
Jira Tickets
🎫 DOC-1663
Backports
Can this PR be backported?