Skip to content

Commit

Permalink
docs: DOC-1262 4.4.7 - Notes (#3179)
Browse files Browse the repository at this point in the history 
* docs: DOC-1262

* docs: added new items

* docs: date update
  • Loading branch information
@karl-cardenas-coding
karl-cardenas-coding authored Jul 8, 2024
1 parent 1e6e1b8 commit 71c9bf6
Show file tree
Hide file tree
Showing 2 changed files with 22 additions and 8 deletions.
14 changes: 7 additions & 7 deletions docs/docs-content/release-notes/known-issues.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,6 @@ The following table lists all known issues that are currently active and affecti
| Description | Workaround | Publish Date | Product Component |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | --------------------- |
| Clusters using Cilium and deployed to VMware environments with the VXLAN tunnel protocol may encounter an I/O timeout error. This issue is caused by the VXMNET3 adapter, which is dropping network traffic and resulting in VXLAN traffic being dropped. You can learn more about this issue in the [Cilium's GitHub issue #21801](https://github.com/cilium/cilium/issues/21801). | Review the [Cilium Troubleshooting](../integrations/cilium.md#io-timeout-error-on-vmware) section for workarounds. | June 27, 2024 | Packs, Clusters, Edge |
| When you upgrade VerteX from version 4.3.x to 4.4.x, a few system pods may remain unhealthy and experience _CrashLoopBackOff_ errors. This issue only impacts VMware vSphere-based installations and occurs because the internal Mongo DNS is incorrectly configured in the configserver ConfigMap. | Refer to the [Mongo DNS Configmap Value is Incorrect](../troubleshooting/palette-upgrade.md#mongo-dns-configmap-value-is-incorrect) troubleshooting guide for detailed workaround steps. This issue may also impact Enterprise Cluster backup operations. | June 24, 2024 | VerteX |
| [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 |
Expand Down Expand Up @@ -47,9 +46,10 @@ The following table lists all known issues that are currently active and affecti
The following table lists all known issues that have been resolved and are no longer affecting users. Refer to the table
for information on the fix version and the date the issue was resolved.

| Description | Publish Date | Product Component | Fix Version |
| -------------------------------------------------------------------------------------------------------- | ----------------- | ----------------- | ----------- |
| 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 |
| MAAS clusters are failing to deploy when the default image endpoint is not set in an airgap environment. | February 26, 2024 | Clusters | 4.2.13 |
| Description | Publish Date | Product Component | Fix Version |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------------- | ----------- |
| When you upgrade VerteX from version 4.3.x to 4.4.x, a few system pods may remain unhealthy and experience _CrashLoopBackOff_ errors. This issue only impacts VMware vSphere-based installations and occurs because the internal Mongo DNS is incorrectly configured in the configserver ConfigMap. | June 29, 2024 | Self-Hosted, VerteX | 4.4.7 |
| 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 |
| MAAS clusters are failing to deploy when the default image endpoint is not set in an airgap environment. | February 26, 2024 | Clusters | 4.2.13 |
16 changes: 15 additions & 1 deletion docs/docs-content/release-notes/release-notes.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,21 @@ tags: ["release-notes"]

<ReleaseNotesVersions />

## Jun 15, 2024 - Release 4.4.0 - 4.4.4
## Jul 7, 2024 - Release 4.4.7

#### Bug Fixes

- Fixed an issue where Edge hosts would lose the local network configuration after adding a node to the cluster.

- Fixed an issue where cluster profile manifest layers were switched, and as a result, different manifest layer YAML
files were applied at the wrong time.

- Fixed an issue occurring with self-hosted Palette and VerteX upgrading to 4.4. x. Mongo DNS was incorrectly configured
in the configserver ConfigMap, resulting in pod errors.

- Fixed an issue where the airgap setup script failed to push all the compressed images to the local registry.

## Jun 15, 2024 - Release 4.4.0 - 4.4.6

<!-- prettier-ignore -->
This release contains various new features and improvements. One new feature is the introduction of
Expand Down

0 comments on commit 71c9bf6

Please sign in to comment.