4.4 Release Notes

docs/docs-content/automation/crossplane/crossplane.md

@@ -23,7 +23,7 @@ provider API to request the creation of the resource within the provider's envir
 
 You can use the Palette Crossplane Provider to interact with the Palette API and create resources declaratively.
 
-Refer to the [Palette Provider](https://marketplace.upbound.io/providers/crossplane-contrib/provider-palette/v0.12.0)
+Refer to the [Palette Provider](https://marketplace.upbound.io/providers/crossplane-contrib/provider-palette/latest)
 page for a complete list of managed resources and examples.
 
 ## Get Started

docs/docs-content/release-notes/known-issues.md

@@ -16,6 +16,9 @@ The following table lists all known issues that are currently active and affecti
 
 | Description                                                                                                                                                                                                                                                                                                                                         | Workaround                                                                                                                                                                                                                                                                     | Publish Date   | Product Component |
 | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | ----------------- |
+| [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 1, 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 1, 2024   | Packs             |
+| Clusters usig [MicroK8s](../integrations/microk8s.md) as the Kubernetes distribution, using the `RollingUpgrade` strategy for clusters with less than three control plane nodes may cause the API server to be down during the upgrade, making the cluster inaccessible.                                                                            | A workaround is to deploy clusters with three or more control plane nodes.                                                                                                                                                                                                     | June 1, 2024   | Packs             |
 | 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          |
 | K3s version 1.27.7 has been marked as _Deprecated_. This version has a known issue that causes clusters to crash.                                                                                                                                                                                                                                   | Upgrade to a newer version of K3s to avoid the issue, such as versions 1.26.12, 1.28.5, and 1.27.11. You can learn more about the issue in the [K3s GitHub issue](https://github.com/k3s-io/k3s/issues/9047) page.                                                             | April 14, 2024 | Packs, Clusters   |