diff --git a/docs/docs-content/clusters/edge/edgeforge-workflow/prepare-user-data.md b/docs/docs-content/clusters/edge/edgeforge-workflow/prepare-user-data.md index 726a3f75c58..083bcc8438e 100644 --- a/docs/docs-content/clusters/edge/edgeforge-workflow/prepare-user-data.md +++ b/docs/docs-content/clusters/edge/edgeforge-workflow/prepare-user-data.md @@ -184,19 +184,19 @@ subject to change. For production workloads, create the `.arg` and `user-data` f the vendor-specific driver or command-line interface (CLI) installed on the Edge host. Multi-Instance GPU (MIG) data can only be retrieved for Nvidia devices with the `nvidia-smi` CLI installed. - ```yaml - #cloud-config - stages: - initramfs: - - users: - USERNAME: - passwd: ****** - groups: - - sudo - ssh_authorized_keys: - - ssh-rsa AAAAB3N… - name: Create user and assign SSH key - ``` +```yaml +#cloud-config +stages: + initramfs: + - users: + USERNAME: + passwd: ****** + groups: + - sudo + ssh_authorized_keys: + - ssh-rsa AAAAB3N… + name: Create user and assign SSH key +``` #### Configure Proxy Settings (Optional) @@ -241,54 +241,54 @@ subject to change. For production workloads, create the `.arg` and `user-data` f installation is complete and before the restart happens. Otherwise, the Edge host might start the installation process again. - #### Configure Users + #### Configure Users -11. If you would like to have SSH access to your Edge host, you must configure Operating System (OS) users on your Edge - host. You can do this using the `stages.initramfs.users` block. Replace `USERNAME` with the name of your user and - replace the value of the password with your password. You can also add the user to user groups, or add SSH keys to - the list of authorized keys for that user. +8. If you would like to have SSH access to your Edge host, you must configure Operating System (OS) users on your Edge + host. You can do this using the `stages.initramfs.users` block. Replace `USERNAME` with the name of your user and + replace the value of the password with your password. You can also add the user to user groups, or add SSH keys to + the list of authorized keys for that user. - ```yaml - #cloud-config - stages: - initramfs: - - users: - USERNAME: - passwd: ****** - groups: - - sudo - ssh_authorized_keys: - - ssh-rsa AAAAB3N… - name: Create user and assign SSH key - ``` + ```yaml + #cloud-config + stages: + initramfs: + - users: + USERNAME: + passwd: ****** + groups: + - sudo + ssh_authorized_keys: + - ssh-rsa AAAAB3N… + name: Create user and assign SSH key + ``` - #### Configure Proxy Settings (Optional) + #### Configure Proxy Settings (Optional) -12. Optionally, you can configure HTTP/HTTPS proxy settings for your Edge host. This instructs the Edge host OS as well - as the Palette agent to use the proxy server for outbound communications. Use the parameters from the table below to - configure proxy settings for your Edge host. +9. Optionally, you can configure HTTP/HTTPS proxy settings for your Edge host. This instructs the Edge host OS as well + as the Palette agent to use the proxy server for outbound communications. Use the parameters from the table below to + configure proxy settings for your Edge host. - These settings are different from the proxy settings you provide to the `.arg` file. The settings in the `.arg` file - apply to the builder machine during the build process, while the settings in `user-data` apply to the Edge host - after installation. + These settings are different from the proxy settings you provide to the `.arg` file. The settings in the `.arg` file + apply to the builder machine during the build process, while the settings in `user-data` apply to the Edge host after + installation. - | Parameter | Description | - | ------------------------ | ------------------------------------------------------------------------------------- | - | `siteNetwork.httpProxy` | The URL of the HTTP proxy endpoint. | - | `siteNetwork.httpsProxy` | The URL of the HTTPS proxy endpoint. | - | `siteNetwork.noProxy` | The list of IP addresses or CIDR ranges to exclude routing through the network proxy. | + | Parameter | Description | + | ------------------------ | ------------------------------------------------------------------------------------- | + | `siteNetwork.httpProxy` | The URL of the HTTP proxy endpoint. | + | `siteNetwork.httpsProxy` | The URL of the HTTPS proxy endpoint. | + | `siteNetwork.noProxy` | The list of IP addresses or CIDR ranges to exclude routing through the network proxy. | - :::warning + :::warning - The proxy settings in user data configure Palette services to use the proxy network. However, these settings do not - automatically apply to application workloads. To configure applications to use the proxy configurations, refer to - [Configure Applications to Use Proxy Server](../../cluster-management/cluster-proxy.md). + The proxy settings in user data configure Palette services to use the proxy network. However, these settings do not + automatically apply to application workloads. To configure applications to use the proxy configurations, refer to + [Configure Applications to Use Proxy Server](../../cluster-management/cluster-proxy.md). - ::: + ::: - #### Configure Post-Installation Behavior (Optional) + #### Configure Post-Installation Behavior (Optional) -13. You can use some parameters of the `install` block to configure what you would like the Edge host to do after +10. You can use some parameters of the `install` block to configure what you would like the Edge host to do after installation is complete. The default behavior for the Edge host is to stay on the "Installation Complete" screen, but you can configure it to power off or restart automatically. For example, the following configuration instructs the Edge host to power off automatically post-installation. diff --git a/docs/docs-content/enterprise-version/install-palette/install-on-kubernetes/install.md b/docs/docs-content/enterprise-version/install-palette/install-on-kubernetes/install.md index eecab1aba26..e49a99d9687 100644 --- a/docs/docs-content/enterprise-version/install-palette/install-on-kubernetes/install.md +++ b/docs/docs-content/enterprise-version/install-palette/install-on-kubernetes/install.md @@ -750,7 +750,7 @@ Use the following steps to validate the Palette installation. the IP address of the load balancer. 2. Log in using the credentials you received from our support team. After login, you will be prompted to create a new - password. Enter a new password and save your changes. You will be redirected to the Palette system console. + password. Enter a new password and save your changes. You will be redirected to the Palette system console. 3. Open a terminal session and issue the following command to verify the Palette installation. The command should return a list of deployments in the `cp-system`, `hubble-system`, `ingress-nginx`, `jet-system` , and `ui-system` diff --git a/docs/docs-content/release-notes/release-notes.md b/docs/docs-content/release-notes/release-notes.md index dbf8fd8510d..9a43ad17724 100644 --- a/docs/docs-content/release-notes/release-notes.md +++ b/docs/docs-content/release-notes/release-notes.md @@ -11,6 +11,22 @@ tags: ["release-notes"] +## March XX, 2026 - Release 4.7.X + +### Improvements + + + +- The internal Palette [Go versions](https://go.dev/doc/devel/release) have been upgraded to 1.24.12 and 1.25.7, + depending on the component, addressing [CVE-2025-68121](https://nvd.nist.gov/vuln/detail/cve-2025-68121). + +### Bug Fixes + + + +- Fixed an issue that caused [Local UI](../clusters/edge/local-ui/local-ui.md) to display sensitive pack values returned + by the [Palette API](/api/introduction). + ## February 12, 2026 - Release 4.7.31 ### Improvements diff --git a/package.json b/package.json index c91276010c7..0cf3440c66b 100644 --- a/package.json +++ b/package.json @@ -127,4 +127,4 @@ "engines": { "node": ">=20.0" } -} \ No newline at end of file +} diff --git a/vale-spellcheck-ignore.txt b/vale-spellcheck-ignore.txt index f422df67214..8cb1f8d7307 100644 --- a/vale-spellcheck-ignore.txt +++ b/vale-spellcheck-ignore.txt @@ -23,4 +23,3 @@ docs/docs-content/clusters/public-cloud/gcp/required-permissions.md:120:105:Vale docs/docs-content/clusters/public-cloud/aws/eks.md:285:84:Vale.Spelling:Did you really mean 'Nodepool'? docs/docs-content/clusters/public-cloud/aws/eks.md:323:16:Vale.Spelling:Did you really mean 'Nodepool'? docs/docs-content/release-notes/release-notes.md:470:19:Vale.Spelling:Did you really mean 'Loadbalancer'? -