Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: release notes 4.3.11 #3452

Merged
merged 10 commits into from
Jul 31, 2024
Merged

docs: release notes 4.3.11 #3452

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
6436612
docs: add addressed list
lennessyy Jul 22, 2024
439a9c4
docs: add more fixed issues
lennessyy Jul 22, 2024
1fa264f
docs: update fixed issues
lennessyy Jul 23, 2024
45dbce4
Merge branch 'version-4-3' into rn-4-3-11
lennessyy Jul 23, 2024
4650d2e
Apply suggestions from code review
lennessyy Jul 23, 2024
a7c443b
docs: add improvement heading
lennessyy Jul 23, 2024
63b4b04
Merge branch 'version-4-3' of github.com:spectrocloud/librarium into …
karl-cardenas-coding Jul 26, 2024
e83ec8c
chore: update release notes date
karl-cardenas-coding Jul 26, 2024
5b930ed
docs: note about dedicated saas
lennessyy Jul 31, 2024
a7a680e
Merge branch 'version-4-3' into rn-4-3-11
lennessyy Jul 31, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/docs-content/release-notes/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,14 +29,12 @@ The following table lists all known issues that are currently active and affecti
| [Sonobuoy](../clusters/cluster-management/compliance-scan.md#conformance-testing) scans fail to generate reports on airgapped Palette Edge clusters. | No workaround is available. | June 24, 2024 | Edge |
| Clusters configured with OpenID Connect (OIDC) at the Kubernetes layer encounter issues when authenticating with the [non-admin Kubeconfig file](../clusters/cluster-management/kubeconfig.md#cluster-admin). Kubeconfig files using OIDC to authenticate will not work if the SSL certificate is set at the OIDC provider level. | Use the admin Kubeconfig file to authenticate with the cluster, as it does not use OIDC to authenticate. | June 21, 2024 | Clusters |
| During the platform upgrade from Palette 4.3 to 4.4, Virtual Clusters may encounter a scenario where the pod `palette-controller-manager` is not upgraded to the newer version of Palette. The virtual cluster will continue to be operational, and this does not impact its functionality. | Refer to the [Controller Manager Pod Not Upgraded](../troubleshooting/palette-dev-engine.md#scenario---controller-manager-pod-not-upgraded) troubleshooting guide. | June 15, 2024 | Virtual Clusters |
| The VerteX enterprise cluster is unable to complete backup operations. | No workaround is available. | June 15, 2024 | VerteX |
| Edge hosts with FIPS-compliant RHEL Operating System (OS) distribution may encounter the error where the `systemd-resolved.service` service enters the **failed** state. This prevents the nameserver from being configured, which will result in cluster deployment failure. | Refer to [TroubleShooting](../troubleshooting/edge.md#scenario---systemd-resolvedservice-enters-failed-state) for a workaround. | June 15, 2024 | Edge |
| The GKE cluster's Kubernetes pods are failing to start because the Kubernetes patch version is unavailable. This is encountered during pod restarts or node scaling operations. | Deploy a new cluster and use a GKE cluster profile that does not contain a Kubernetes pack layer with a patch version. Migrate the workloads from the existing cluster to the new cluster. This is a breaking change introduced in Palette 4.4.0 | June 15, 2024 | Packs, Clusters |
| [MicroK8s](../integrations/microk8s.md) does not support multi-node control plane clusters. The upgrade strategy, `InPlaceUpgrade`, is the only option available for use. | No workaround is available. | June 15, 2024 | Packs |
| Clusters using [MicroK8s](../integrations/microk8s.md) as the Kubernetes distribution, the control plane node fails to upgrade when using the `InPlaceUpgrade` strategy for sequential upgrades, such as upgrading from version 1.25.x to version 1.26.x and then to version 1.27.x. | Refer to the [Control Plane Node Fails to Upgrade in Sequential MicroK8s Upgrades](../troubleshooting/pack-issues.md) troubleshooting guide for resolution steps. | June 15, 2024 | Packs |
| Azure IaaS clusters are having issues with deployed load balancers and ingress deployments when using Kubernetes versions 1.29.0 and 1.29.4. Incoming connections time out as a result due to a lack of network path inside the cluster. Azure AKS clusters are not impacted. | Use a Kubernetes version lower than 1.29.0 | June 12, 2024 | Clusters |
| OIDC integration with Virtual Clusters is not functional. All other operations related to Virtual Clusters are operational. | No workaround is available. | Jun 11, 2024 | Virtual Clusters |
| The VerteX enterprise cluster is unable to complete backup operations. | No workaround is available. | June 6, 2024 | VerteX |
| Deploying self-hosted Palette or VerteX to a vSphere environment fails if vCenter has standalone hosts directly under a Datacenter. Persistent Volume (PV) provisioning fails due to an upstream issue with the vSphere Container Storage Interface (CSI) for all versions before v3.2.0. Palette and VerteX use the vSphere CSI version 3.1.2 internally. The issue may also occur in workload clusters deployed on vSphere using the same vSphere CSI for storage volume provisioning. | If you encounter the following error message when deploying self-hosted Palette or VerteX: `'ProvisioningFailed failed to provision volume with StorageClass "spectro-storage-class". Error: failed to fetch hosts from entity ComputeResource:domain-xyz` then use the following workaround. Remove standalone hosts directly under the Datacenter from vCenter and allow the volume provisioning to complete. After the volume is provisioned, you can add the standalone hosts back. You can also use a service account that does not have access to the standalone hosts as the user that deployed Palette. | May 21, 2024 | Self-Hosted |
| Conducting cluster node scaling operations on a cluster undergoing a backup can lead to issues and potential unresponsiveness. | To avoid this, ensure no backup operations are in progress before scaling nodes or performing other cluster operations that change the cluster state | April 14, 2024 | Clusters |
| Palette automatically creates an AWS security group for worker nodes using the format `<cluster-name>-node`. If a security group with the same name already exists in the VPC, the cluster creation process fails. | To avoid this, ensure that no security group with the same name exists in the VPC before creating a cluster. | April 14, 2024 | Clusters |
Expand All @@ -56,6 +54,7 @@ for information on the fix version and the date the issue was resolved.

| Description | Publish Date | Product Component | Fix Version |
| -------------------------------------------------------------------------------------------------------- | ----------------- | ----------------- | ----------- |
| The VerteX enterprise cluster is unable to complete backup operations. | June 15, 2024 | VerteX | 4.3.11 |
| Clusters are failing to start on AWS EKS when using the AWS VPC CNI pack and Kubernetes versions 1.28. | February 26, 2024 | Packs, Clusters | 4.2.13 |
| The Kubernetes Dashboard fails to load when added to a cluster profile and deployed. | February 26, 2024 | Packs | 4.2.13 |
| Clusters using MicroK8s are failing to launch pods due to a mismatch in node affinity labels. | February 26, 2024 | Packs, Clusters | 4.2.13 |
Expand Down
38 changes: 38 additions & 0 deletions docs/docs-content/release-notes/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,44 @@ tags: ["release-notes"]

<ReleaseNotesVersions />

## July 30, 2024 - Release 4.3.11

:::info

This patch release will not be applied to Palette SaaS. It will be applied to dedicated SaaS environments only. If you
are interested in upgrading to this patch release, please reach out to our support team at [email protected].

:::

### Bug Fixes

- Fixed an issue that sometimes would cause Edge clusters with three control plane nodes and one worker node with the
local Harbor registry enabled to be stuck in the **Provisioning** state.

- Resolved several CVEs in the previous release. For a complete list of current CVEs, refer to
[CVE Report](../security-bulletins/reports/reports.md).

- Fixed an issue that caused clusters to experience problems in communicating with Palette through gPRC using domain
names and port 443, resulting in clusters appearing in an **Unhealthy** state.

- Resolved a VerteX issue that sometimes would prevent users from updating the cluster profile of an active cluster.

- Addressed an issue that prevented cluster profiles from being created after performing a database restore operation on
a self-hosted Palette instance.

- Resolved the issue that caused VerteX enterprise cluster to be unable to complete backup operations.

- Fixed a VerteX issue that caused cluster deployments failures to AWS EKS.

- Fixed an issue that caused the Palette agents to upgrade to 4.4 even when platform upgrades are paused.

- Resolved an issue that prevented users from updating system profiles using the System Console in a self-hosted
instance of Palette.

lennessyy marked this conversation as resolved.
Show resolved Hide resolved
### Improvement

- Added the **Error** status to backup operations in the System Console in self-hosted instances of Palette.

## May 19, 2024 - Release 4.3.8

### Bug Fixes
Expand Down