Skip to content

docs: release 4.7.a #7745

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

Merged
achuribooks merged 47 commits into from
Aug 17, 2025
Merged

docs: release 4.7.a #7745

Show file tree
Hide file tree
Changes from 14 commits
Commits
Show all changes
47 commits
Select commit Hold shift + click to select a range
f0b3d70
docs: release 4.7.a
addetz Jul 28, 2025
6486fa1
Merge branch 'master' into release-4-7-a
addetz Jul 28, 2025
424c390
Merge branch 'master' into release-4-7-a
caroldelwing Jul 30, 2025
4d0d969
docs: Add packs deletion order (#7580)
svetlana-efimova Jul 30, 2025
6bef84e
Merge branch 'master' into release-4-7-a
benradstone Jul 31, 2025
fd0a885
Merge branch 'master' into release-4-7-a
benradstone Aug 1, 2025
afff3df
docs: remove Spectro Addon Repo references DOC-2066 (#7581)
caroldelwing Aug 1, 2025
a55a1eb
docs: Remove Tech Preview for Harbor Edge-Native Config pack (#7635)
svetlana-efimova Aug 1, 2025
de2100b
docs: PCP-4752: MAAS Node Pool AZ Breaking Change (#7659)
achuribooks Aug 4, 2025
6f0ebb5
docs: remore preview from remote shell (#7701)
lennessyy Aug 4, 2025
1e3e62a
PCP-4774 - EKS worker node customisation (#7692)
benradstone Aug 5, 2025
952dbe5
DOC-2063 - Karpenter read-only support for EKS (#7714)
benradstone Aug 6, 2025
5a7574b
docs: PCP-4752: Updated Breaking Change re: MAAS AZ Node Pool (#7715)
achuribooks Aug 6, 2025
a0c5822
Merge branch 'master' into docs-rel-4-7-a
addetz Aug 6, 2025
ddff0b8
Optimised images with calibre/image-actions
vault-token-factory-spectrocloud[bot] Aug 6, 2025
57ba1e8
Optimised images with calibre/image-actions
vault-token-factory-spectrocloud[bot] Aug 6, 2025
2dc032f
Optimised images with calibre/image-actions
vault-token-factory-spectrocloud[bot] Aug 6, 2025
98ad0f7
Optimised images with calibre/image-actions
vault-token-factory-spectrocloud[bot] Aug 6, 2025
76337b4
docs: Add Canonical K8s pack for MAAS (#7713)
svetlana-efimova Aug 6, 2025
01862fd
Merge branch 'master' into docs-rel-4-7-a
benradstone Aug 7, 2025
3ab95f7
PEM-7798: auto cluster role bindings (#7750)
Linus-SpectroCloud Aug 8, 2025
a3d6225
ci: auto-formatting prettier issues
Linus-SpectroCloud Aug 8, 2025
fbc8c13
docs: add AI pack type DOC-2065 (#7749)
caroldelwing Aug 8, 2025
76f25e5
docs: add 4.7.a Palette + Edge APIs DOC-1927 (#7781)
addetz Aug 11, 2025
3a6ae60
Merge branch 'master' into docs-rel-4-7-a
addetz Aug 11, 2025
820d91c
docs: add consoleBaseAddress guide PEM-8211 PEM-8232 (#7780)
addetz Aug 12, 2025
25d00e2
(docs-rel-4-7-a) PEM-7965: Documenting GPU quotas (#7782)
Linus-SpectroCloud Aug 12, 2025
f74c1ce
docs: add known issue PE-7313 (#7798)
lennessyy Aug 12, 2025
6390825
docs: add known issue PE-7303 (#7799)
lennessyy Aug 12, 2025
bdf09b4
Merge branch 'master' into docs-rel-4-7-a
benradstone Aug 13, 2025
958b564
Merge branch 'master' into docs-rel-4-7-a
benradstone Aug 13, 2025
826e2eb
Doc 2062 artifact studio enhancements (#7802)
Linus-SpectroCloud Aug 13, 2025
2f3853b
Merge branch 'master' into docs-rel-4-7-a
benradstone Aug 14, 2025
90392a6
DOC-2024 - Management Appliance Upgrade Steps (#7804)
benradstone Aug 14, 2025
60b1f82
docs: DOC-1922: 4.7.a OSS Licenses (#7811)
achuribooks Aug 14, 2025
0c649c3
PCP-4774 - Additional examples for EKS node customization (#7821)
benradstone Aug 14, 2025
96a5582
docs: DOC-2100: Known Issue: Overlay Cluster Static FDB Entry Logs (#…
achuribooks Aug 14, 2025
9f6c08b
docs: Add Cilium annotations known issue (#7818)
svetlana-efimova Aug 14, 2025
59b35a2
DOC-2098 - Karpenter Support Limitations (#7823)
benradstone Aug 15, 2025
722810f
Merge branch 'master' into docs-rel-4-7-a
benradstone Aug 15, 2025
7d7891e
docs: vmo role creation DOC-2001 (#7831)
addetz Aug 15, 2025
fc099bd
docs: add 4.7.a release notes DOC-1923 DOC-1928 (#7783)
addetz Aug 15, 2025
52d8db2
docs: DOC-1926: Updated Airgap Packs and OVAs for 4.7.a (#7829)
achuribooks Aug 15, 2025
6f77c4b
docs: DOC-2102: Remove NIC and vip_interface Requirements for Network…
achuribooks Aug 15, 2025
71bd2b0
docs: DOC-1924 & DOC-1925: Release + Compatability Matrix Updates (#7…
achuribooks Aug 17, 2025
8272630
Merge branch 'master' into docs-rel-4-7-a
achuribooks Aug 17, 2025
c2e5afb
docs: DOC-2061 (#7852)
lennessyy Aug 17, 2025
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
4 changes: 0 additions & 4 deletions docs/docs-content/clusters/edge/cluster-management/remote-shell.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,6 @@ use a remote shell session to access your centrally managed Edge host. This conn

![Diagram of the relationship between user, Palette, and Edge host in Remote Shell](/clusters_edge_cluster-mgmt_remote-shell.webp)

:::preview

:::

You can generate temporary user credentials with root privileges or use an existing user on your Edge host. Temporary
users have root privilege on the Edge host, allowing you the permissions often required to troubleshoot, but they must
be enabled per Edge host by someone with sufficient permissions.
Expand Down
10 changes: 10 additions & 0 deletions docs/docs-content/clusters/public-cloud/aws/architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,16 @@ managedControlPlane:
disableAssociateOIDCProvider: true
```

### Karpenter Support

Nodes provisioned through [Karpenter](https://karpenter.sh/docs/) are visible in Palette and supported for read-only
operations, such as billing and monitoring. However, [Day-2 operations](../../cluster-management/cluster-management.md)
are not supported.

The **Managed by Karpenter** banner is displayed for any node pools that are provisioned using Karpenter.

![Karpenter node in Palette](/public-cloud_aws_architecture_managed-by-karpenter.webp)

## AWS Instance Type and Pod Capacity

Choose the instance type and the number of instances to be launched by calculating the number of expected pods. You
Expand Down
14 changes: 7 additions & 7 deletions docs/docs-content/clusters/public-cloud/aws/eks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -293,13 +293,13 @@ an AWS account. This section guides you on how to create an EKS cluster in AWS t

#### Cloud Configuration Settings

| **Parameter** | **Description** |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Instance Option** | Choose a pricing method:<br /><br />- **On-Demand** - Provides stable and uninterrupted compute capacity at a higher cost.<br />- **Spot** - Allows you to bid for unused EC2 capacity at a lower cost.<br />We recommend you base your choice on your application's requirements. |
| **Instance Type** | Select the instance type to use for all nodes in the node pool. |
| **Amazon Machine Image (AMI) Type** | Specify a base AMI to use for your worker nodes: **AL2_x86_64**, **AL2_x86_64_GPU**, **AL2023_x86_64_STANDARD**, **AL2023_x86_64_NEURON**, or **AL2023_x86_64_NVIDIA**. An **AL2_x86_64** AMI is used by default if no AMI is selected. <br /><br /> The AMI type cannot be modified post-deployment. Nodes using an Amazon Linux 2023 (AL2023) AMI must configure IAM Roles for Service Accounts (IRSA) if you are using AWS CSI packs such as Amazon EBS CSI, Amazon EFS CSI, and Amazon Cloud Native. IRSA is also required if using the AWS Application Loadbalancer. Refer to the [Scenario - PV/PVC Stuck in Pending Status for EKS Cluster Using AL2023 AMI](../../../troubleshooting/cluster-deployment.md#scenario---pvpvc-stuck-in-pending-status-for-eks-cluster-using-al2023-ami) troubleshooting guide for further information. |
| **Enable Nodepool Customization (Optional)** | Activate additional node pool customization options: <br /><br />- **Amazon Machine Image (AMI) ID (Optional)** - Use a pre-configured VM image by providing the ID value of the AMI. The AMI ID can be updated post-deployment, but the base AMI type must always match the type specified in the **Amazon Machine Image (AMI) Type** field, and the AMI must be compatible with the Kubernetes version specified in the [cluster profile](../../../profiles/cluster-profiles/cluster-profiles.md). <br />- **Disk Type (Optional)** - Specify the disk type to use. |
| **Root Disk size (GB)** | Choose a disk size based on your requirements. The default size is `60`. |
| **Parameter** | **Description** |
| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Instance Option** | Choose a pricing method:<br /><br />- **On-Demand** - Provides stable and uninterrupted compute capacity at a higher cost.<br />- **Spot** - Allows you to bid for unused EC2 capacity at a lower cost.<br />We recommend you base your choice on your application's requirements. |
| **Instance Type** | Select the instance type to use for all nodes in the node pool. |
| **Amazon Machine Image (AMI) Type** | Specify a base AMI to use for your worker nodes: <br /> - **AL2_x86_64** (used by default if none selected) <br /> - **AL2_x86_64_GPU** <br /> - **AL2023_x86_64_STANDARD** <br /> - **AL2023_x86_64_NEURON** <br /> - **AL2023_x86_64_NVIDIA** <br /><br /> The AMI type cannot be modified post-deployment. Refer to the <VersionedLink text="Node Customization" url="/integrations/packs/?pack=kubernetes-eks&tab=custom#node-customization"/> section of the Kubernetes EKS pack for configurable options available for these AMIs. <br /><br /> If using an Amazon Linux 2023 (AL2023) AMI and using an AWS CSI pack such as Amazon EBS CSI, Amazon EFS CSI, or Amazon Cloud Native, you must configure IAM Roles for Service Accounts (IRSA). IRSA is also required if using the AWS Application Loadbalancer. Refer to the [Scenario - PV/PVC Stuck in Pending Status for EKS Cluster Using AL2023 AMI](../../../troubleshooting/cluster-deployment.md#scenario---pvpvc-stuck-in-pending-status-for-eks-cluster-using-al2023-ami) troubleshooting guide for further information. |
| **Enable Nodepool Customization (Optional)** | Activate additional node pool customization options: <br /><br />- **Amazon Machine Image (AMI) ID (Optional)** - Use a pre-configured VM image by providing the ID value of the AMI. The AMI ID can be updated post-deployment, but the base AMI type must always match the type specified in the **Amazon Machine Image (AMI) Type** field, and the AMI must be compatible with the Kubernetes version specified in the [cluster profile](../../../profiles/cluster-profiles/cluster-profiles.md). <br />- **Disk Type (Optional)** - Specify the disk type to use. |
| **Root Disk size (GB)** | Choose a disk size based on your requirements. The default size is `60`. |

#### Fargate Profiles

Expand Down
6 changes: 3 additions & 3 deletions docs/docs-content/integrations/cloudanix.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,14 +54,14 @@ As a final step, apply the cluster profile to your cluster.
## Terraform

```hcl
data "spectrocloud_registry" "public_add_on_repo" {
name = "Spectro Addon Repo"
data "spectrocloud_registry" "public_registry" {
name = "Public Repo"
}

data "spectrocloud_pack_simple" "cloudanix" {
name = "cloudanix"
version = "0.0.2"
type = "helm"
registry_uid = data.spectrocloud_registry.public_add_on_repo.id
registry_uid = data.spectrocloud_registry.public_registry.id
}
```
6 changes: 3 additions & 3 deletions docs/docs-content/integrations/gatekeeper.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,14 +43,14 @@ tags: ["packs", "open-policy-agent", "security"]
You can retrieve details about the Gatekeeper pack by using the following Terraform code.

```hcl
data "spectrocloud_registry" "public_addon_registry" {
name = "Spectro Addon Repo"
data "spectrocloud_registry" "community_registry" {
name = "Palette Community Registry"
}

data "spectrocloud_pack_simple" "gatekeeper" {
name = "gatekeeper"
version = "3.8.0"
type = "helm"
registry_uid = data.spectrocloud_registry.public_addon_registry.id
registry_uid = data.spectrocloud_registry.community_registry.id
}
```
4 changes: 0 additions & 4 deletions docs/docs-content/integrations/harbor-edge-native-config.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,10 +21,6 @@ The Harbor Edge-Native Config pack is a system application pack. When you provis
includes this pack, Palette automatically chooses the latest version of Harbor supported by Palette to install on the
cluster. You cannot manually choose a version of this pack.

:::preview

:::

## Enable Harbor to Protect Against Outage

You can use Harbor in an Edge cluster that is connected to external networks. Harbor stores all container images
Expand Down
Loading
Loading