Collection of 4.2 items

docs/docs-content/clusters/cluster-management/image-swap.md

@@ -105,6 +105,18 @@ imageSwap:
 
 The examples provided are intended to help you get started. Refer to the official [Image Swap configuration](https://github.com/phenixblue/imageswap-webhook/blob/master/README.md#configuration) for more examples and information.
 
+## Limitations
+
+- Image swap is only supported for managed Kubernetes clusters, such as Amazon EKS, Azure AKS, and Google GKE. 
+
+- Self-hosted Palette and VerteX installations can support image swap functionality for non-managed Kubernetes clusters. This requires mirror registries to be specified during the self-hosted Palette or VerteX installation. Refer to the [Self-Hosted Palette Installation](../../enterprise-version/install-palette/install-palette.md) or [VerteX Install](../../vertex/install-palette-vertex/install-palette-vertex.md) guide for more information.
+
+  The following table summarizes the image swap support for different scenarios and what Palette deployment type is required.
+
+  | Image Swap Scenario | Supported in Palette SaaS? | Supported in Self-Hosted Palette? | Supported in VerteX? | Description |
+  | --- | --- | --- | --- | --- |
+  | Managed Kubernetes Cluster |  :white_check_mark: | :white_check_mark: | :white_check_mark: | Image swap is supported for managed Kubernetes clusters, such as AKS, EKS, and GKE. |
+  | Non-Managed Kubernetes Cluster | :x: | :white_check_mark: | :white_check_mark: | Image swap is supported for non-managed Kubernetes clusters. This requires mirror registries to be specified during the self-hosted Palette or VerteX installation.  |
 
 ## Image Swap with Palette
 

docs/docs-content/clusters/palette-virtual-clusters/palette-virtual-clusters.md

@@ -27,11 +27,21 @@ The following Kubernetes distributions are supported for virtual clusters:
 | **Name** | **Description** |
 | --- | --- |
 | **K3s** | [K3s](https://k3s.io) is a lightweight, certified Kubernetes distribution designed for production workloads. |
-| **CNCF K8s**| The Cloud Native Computing Foundation (CNCF) [Kubernetes distribution](https://www.cncf.io/projects/kubernetes). |
+| **Kubernetes**| The Cloud Native Computing Foundation (CNCF) [Kubernetes distribution](https://www.cncf.io/projects/kubernetes). |
 
 
 Refer to the [Create and Manager Cluster Groups](../cluster-groups/create-cluster-group.md#palette-virtual-cluster-configuration) to learn how to configure your cluster group to use a specific Kubernetes distribution.
 
+### Minimum Resource Requirements
+
+The following table lists the minimum resource requirements for virtual clusters and the underlying Kubernetes distribution.
+
+ |**Resource Type** | **Default**   |**K3s Minimum Limit**| **Kubernetes Minimum Limit**|
+ |------------------------------|-------------------|-----------------| -----------------|
+ | CPU (per request)            | 4                 | 4               | 4               |
+ | Memory (per request)         | 4 GiB             | 3 GiB           | 4 GiB         |
+ | Storage (per request)        | 2 GiB            | 0 GiB           | 2 GiB           |
+
 ## Network Connectivity
 
 Virtual clusters support two network endpoint types: Load Balancer and Ingress. The network endpoint type determines how virtual clusters are exposed to external traffic. You specify the network endpoint type in Cluster Group Settings.

docs/docs-content/devx/devx.md

@@ -24,13 +24,14 @@ To get started with App Mode, give the tutorial [Deploy an Application using Pal
 
 ## Supported Platforms
 
-App Mode is available for the following Palette platforms.
+App Mode is available for the following Palette and VerteX platforms.
 
-| Platform | Supported | Palette Version |
+| Platform | Supported |  Version |
 |---|----|---|
-| SaaS | ✅| `v3.0.0` or greater. |
-| Self-hosted | ✅ | `v3.4.0` or greater. |
-| Airgap Self-hosted | ✅ |`v4.0.0` or greater. |
+| Palette SaaS | ✅| `v3.0.0` or greater. |
+| Self-hosted Palette | ✅ | `v3.4.0` or greater. |
+| Palette Airgap Self-hosted | ✅ |`v4.0.0` or greater. |
+| VerteX | :warning: | `v4.0.0` or greater. Be aware that App Mode is not FIPS compliant. |
 
 
 ## Manage Resources

docs/docs-content/integrations/harbor-edge.md

@@ -173,6 +173,8 @@ The following known issues exist in the Harbor 1.0.0 release.
 
 - The Harbor database pod might fail to start due to file permission issues. This is a [known issue](https://github.com/goharbor/harbor-helm/issues/1676) in the Harbor GitHub repository. Refer to the [Troubleshooting section](#scenario---harbor-db-pod-fails-to-start) for a workaround.   
 
+- A cluster may get stuck in the provisioning state if it uses Longhorn as its storage layer. If this happens, remove the cluster and try again.
+
 </TabItem>
 </Tabs>
 

docs/docs-content/release-notes.md

@@ -20,7 +20,7 @@ Palette 4.2.0 is a release that includes new features and various improvements.
 #### Features
 
 
-- Palette now supports the cloud provider, [Nutanix](https://www.nutanix.com/). You can deploy Kubernetes clusters on Nutanix using Palette. Support for Nutanix is currently under technical preview and subject to change as we continue to improve the integration.
+- Palette now supports the cloud provider, [Nutanix](https://www.nutanix.com/), as a Technical Preview feature. You can deploy Kubernetes clusters on Nutanix using Palette. Technical Preview features are subject to change as we continue to improve the integration. Refer to the [Nutanix](./clusters/data-center/nutanix/nutanix.md) resource to learn more about deploying Nutanix clusters with Palette.
 
 
 - Automatic SSL certificate renewal is now supported for clusters deployed through Palette. In the past, this was a manual action that had to be performed by the user, which also caused node repaves. Palette will now automatically renew the certificate 30 days before the expiration date without triggering a node repave. This feature is available in all supported infrastructure providers except for Edge. For more information, refer to the [Certificate Management](./clusters/cluster-management/certificate-management.md) resource.
@@ -54,6 +54,11 @@ Palette 4.2.0 is a release that includes new features and various improvements.
 
 - The ability to change the underlying node type of a node pool is not available for Google Cloud Platform GKE clusters.
 
+- Clusters launched in VMware vSphere with the Container Network Interface (CNI) Cilium, lose node-to-node connectivity when the vSphere adapter is configured to use VMXNET3. This is a known issue with Cilium and VMXNET3. Refer to the [GitHub issue discussion](https://github.com/cilium/cilium/issues/21801) to learn more about this issue.
+
+
+- Enabling [passkeys](/enterprise-version/system-management/account-management/credentials.md) in a self-hosted Palette instance will cause JSON Web Tokens (JWT) returned by the system API endpoint `/v1/auth/syslogin` to be invalid. Refer to the [Passkeys and API Access](./enterprise-version/system-management/account-management/credentials.md#passkeys-and-api-access) resource for more information on accessing the system API when passkeys are enabled. This issue does not affect the regular Palette API used by clusters and users.
+
 
 ### Edge
 
@@ -63,7 +68,7 @@ Palette 4.2.0 is a release that includes new features and various improvements.
 
 #### Features
 
-- Overlay support for DHCP. Edge clusters can now establish an VxLAN overlay network during cluster creation, and Edge hosts can self-discover the overlay network within a single ethernet broadcast domain. Clusters using this feature will remain operational when the host IP addresses change unexpectedly. Check out the [Enable Overlay Network](clusters/edge/networking/vxlan-overlay.md) resource for more information.
+- Overlay support for DHCP is now available as a Tech Preview feature. Edge clusters can now establish an VxLAN overlay network during cluster creation, and Edge hosts can self-discover the overlay network within a single ethernet broadcast domain. Clusters using this feature will remain operational when the host IP addresses change unexpectedly. Check out the [Enable Overlay Network](clusters/edge/networking/vxlan-overlay.md) resource for more information.
 
 
 - Local registry support. You can deploy a self-hosted [Harbor registry](https://goharbor.io) on your Edge cluster and use the registry to store images for your workloads and initialize a cluster's other edge host nodes. Using a local registry can help you reduce the amount of data transferred over the network, cache images locally, and provide a backup for when internet access is unavailable. 
@@ -78,6 +83,25 @@ Palette 4.2.0 is a release that includes new features and various improvements.
 - Extended [kube-vip customization](https://kube-vip.io/docs/installation/flags/) is now available for new Edge clusters. You can now specify additional kube-vip configuration parameters as part of the Kubernetes pack layer configuration. To learn more about the available kube-vip configuration parameters, refer to the [Publish Cluster Services with Kube-vip](clusters/edge/networking/kubevip.md) resource.
 
 
+
+#### Known Issues
+
+- The following known issues apply to the VxLAN network overlay feature:
+
+  - When adding multiple nodes to an existing cluster with overlay enabled, failure to add one node will block the addition of the other nodes.
+
+  - When deleting an Edge host from a cluster with overlay enabled, ensure the node doesn't have the `palette-webhook` pod on it, or the node will be stuck in the deleting state. You can use the command `kubectl get pods --all-namespaces --output wide` to identify which node the pod `palette-webhook` is on. Reach out to our support team [support@spectrocloud.com](mailto:support@spectrocloud.com) if you need to remove a node with the `palette-webhook` pod on it.
+
+- In a multi-node cluster with [PXK-E](./integrations/kubernetes-edge.md) as the Kubernetes distribution, you cannot change the Network Interface Card (NIC). When you add an Edge host to such a cluster, leave the NIC field as its default value.
+
+- The following known issues apply to [Harbor Edge Native Config](./integrations/harbor-edge.md) when deployed with the [Longhorn](./integrations/longhorn.md) Container Storage Interface (CSI) driver:
+
+  - The Harbor job service pod is in a *Terminating* and *ContainerCreating* state in an Edge Native High Availability (HA) cluster after a Day-2 operation.
+
+  - The Harbor database pod might fail to start due to file permission issues. This is a [known issue](https://github.com/goharbor/harbor-helm/issues/1676) in the Harbor GitHub repository.
+
+  - A cluster may get stuck in the provisioning state. If this happens, remove the cluster and try again.
+
 ### Palette Dev Engine (PDE)
 
 
@@ -110,6 +134,11 @@ Palette 4.2.0 is a release that includes new features and various improvements.
 
 - To better support airgap installs and customers in internet-restricted environments. You can now access Palette documentation offline by using the Palette documentation container. For more information, refer to the [Offline Documentation](./vertex/install-palette-vertex/airgap/offline-docs.md) page.
 
+
+####  Known Issues
+
+- Enabling [passkeys](./vertex/system-management/account-management/credentials.md#add-passkeys) in a VerteX instance will cause JSON Web Tokens (JWT) returned by the system API endpoint `/v1/auth/syslogin` to be invalid. Refer to the [Passkeys and API Access](./vertex/system-management/account-management/credentials.md#passkeys-and-api-access) resource for more information on accessing the system API when passkeys are enabled. This issue does not affect the regular VerteX API used by clusters and users.
+
 ### Terraform
 
 #### Breaking Changes