docs: release 4.8.a

README.md

@@ -515,6 +515,16 @@ Result
 
 ### Admonitions - Warning / Info / Tip / Danger / Tech Preview / Further Guidance
 
+For guidance on using admonitions in our docs, refer to
+[Spectro Cloud Internal Style Guide: Admonitions/Callouts](https://spectrocloud.atlassian.net/wiki/spaces/DE/pages/1765933057/Spectro+Cloud+Internal+Style+Guide#Admonitions%2FCallouts).
+
+To learn more about admonitions in Docusaurus, refer to the
+[Admonitions](https://docusaurus.io/docs/markdown-features/admonitions) guide.
+
+The content must have a new line at the beginning and at the end of the tag.
+
+#### Warning
+
 ```mdx
 :::warning
 
@@ -523,6 +533,8 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
+#### Info
+
 ```mdx
 :::info
 
@@ -531,6 +543,8 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
+#### Tip
+
 ```mdx
 :::tip
 
@@ -539,6 +553,8 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
+#### Danger
+
 ```mdx
 :::danger
 
@@ -547,6 +563,15 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
+#### Tech Preview
+
+The `:::preview` admonition is a custom admonition configured in `docusaurus.config.js` under `admonitions.keywords`.
+
+Unlike other admonition types, you do not need to enter content in the admonition block. By default, the Tech Preview
+admonition generates the message, "This is a Tech Preview feature and is subject to change. Do not use this feature in
+production workloads." This message is hardcoded using `src/theme/Admonition/Type/TechPreview.js`. However, if you need
+to deviate from the template text, you can provide a custom message.
+
 ```mdx
 :::preview
 
@@ -555,6 +580,22 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
+Files in `docs/docs-content` and `docs/api-content` are processed during the build phase. However, partials in the
+`_partials` directory are dynamically imported at runtime. Because of this, custom admonitions defined in
+`docusaurus.config.js` that are used in partials are not rendered, and the custom admonition is ignored.
+
+As a workaround, when using custom admonitions in partials, import and reference the admonition with JSX syntax.
+
+```mdx
+import AdmonitionTypeTechPreview from '@theme/Admonition/Type/TechPreview'; # Import below front matter
+
+<AdmonitionTypeTechPreview /> # Use instead of :::
+```
+
+Note that when used in partials, the default message cannot be overridden.
+
+#### Further Guidance
+
 ```mdx
 :::further
 
@@ -563,12 +604,14 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
-https://docusaurus.io/docs/markdown-features/admonitions
+Like Tech Preview, the Further Guidance admonition is a custom admonition. To use this admonition in partials, you must
+import and reference it with JSX syntax.
 
-The content must have a new line at the beginning and at the end of the tag.
+```mdx
+import AdmonitionTypeFurtherGuidance from '@theme/Admonition/Type/FurtherGuidance'; # Import below front matter
 
-For guidance on using admonitions, refer to
-[Spectro Cloud Internal Style Guide: Admonitions/Callouts](https://spectrocloud.atlassian.net/wiki/spaces/DE/pages/1765933057/Spectro+Cloud+Internal+Style+Guide#Admonitions%2FCallouts).
+<AdmonitionTypeFurtherGuidance /> # Use instead of :::
+```
 
 ### Video
 

_partials/_palette-kubernetes-versions.mdx

@@ -7,6 +7,7 @@ For installations using a Kubernetes cluster, we support any non-EOL (End of Lif
 
 | **Palette Version** <!-- kubernetes-max-version-table --> | **Highest Supported Kubernetes Version** |
 | ------------------- | ---------------------- |
+| <!-- k8s-max-4-8-a --> 4.8.21 | 1.35.5 |
 | <!-- k8s-max-4.8.0 --> 4.8.6 | 1.34.2 |
 | <!-- k8s-max-4-7-c --> 4.7.27 | 1.33.0 |
 | <!-- k8s-max-4.7.b --> 4.7.20 | 1.33.0 |

_partials/cluster-templates/_profile-vs-template.mdx

@@ -3,16 +3,8 @@ partial_category: cluster-templates
 partial_name: profile-vs-template
 ---
 
-import AdmonitionTypeTechPreview from '@theme/Admonition/Type/TechPreview';
-
 Choose between deploying your cluster using individual <VersionedLink text="cluster profiles" url="/profiles/cluster-profiles/" />
-or a single <VersionedLink text="cluster template" url="/cluster-templates" />. 
-
-:::info
-
-<VersionedLink text="Cluster templates" url="/cluster-templates" /> are a Tech Preview feature and can be used only if the **ClusterTemplates** <VersionedLink text="feature flag" url="/enterprise-version/system-management/feature-flags/" /> is enabled.
-
-:::
+or a single <VersionedLink text="cluster template" url="/cluster-templates" />.
 
 <Tabs>
 
@@ -26,18 +18,17 @@ or a single <VersionedLink text="cluster template" url="/cluster-templates" />.
     3. Review the layers of your cluster profile. Use the drop-down menus to select the appropriate cluster profile version, add necessary 
     <VersionedLink text="add-on profiles" url="/profiles/cluster-profiles/create-cluster-profiles/create-addon-profile/" />, and make changes to YAML configuration files as needed. {props.additional_info} When finished, select **Next**.
 
-        :::tip
+        :::info
 
-        For ease of reuse and to persist changes across clusters using the same cluster profile, we recommend <VersionedLink text="creating a new version of your cluster profile" url="/profiles/cluster-profiles/modify-cluster-profiles/version-cluster-profile" /> rather than making inline changes.
+        - Cluster profile versions linked to cluster templates cannot be used in the cluster profile workflow.
+        - For ease of reuse and to persist changes across clusters using the same cluster profile, we recommend <VersionedLink text="creating a new version of your cluster profile" url="/profiles/cluster-profiles/modify-cluster-profiles/version-cluster-profile" /> rather than making inline changes.
 
         :::
 
 </TabItem>
 
 <TabItem value="template" label="Cluster Templates">
 
-    <AdmonitionTypeTechPreview />
-
     1. On the **Cluster setup type** window, choose **Cluster Template > Select Cluster Template**.
 
     2. Select the appropriate cluster template and **Confirm** your selection.

_partials/clusters/_clusters_cluster-settings.mdx

@@ -0,0 +1,15 @@
+---
+partial_category: clusters
+partial_name: cluster-settings
+---
+
+On the **Cluster Settings** page, configure additional
+    options as needed. If you are deploying your cluster using [cluster templates](/cluster-templates), a **Cluster Timezone** is required.
+
+    | **Left Menu Item** | **Additional Information** |
+    | --- | --- |
+    | **Cluster Timezone** | Specify the time zone where your cluster is being deployed. The time zone is used in [maintenance policies](/cluster-templates/create-cluster-template-policies/maintenance-policy) to determine when updates are rolled out to clusters deployed with [cluster templates](/cluster-templates). 
+    | **Manage machines** | Set an [OS patching](/clusters/cluster-management/os-patching) schedule and specify node behavior when creating your cluster, including upgrading your nodes to use the latest OS patch version and allowing reboots. |
+    | **Schedule scans** | Enable any scan options you want Palette to perform and select a scan schedule. Palette supports Kubernetes configuration security, penetration testing, and conformance testing. Refer to [Compliance Scan](/clusters/cluster-management/compliance-scan/#configuration-security) for details on each scan type. |
+    | **Schedule backups** | Schedule backups for your entire cluster or etcd. Refer to [Backup and Restore](/clusters/cluster-management/backup-restore) for more information. |
+    | **RBAC** | Map a set of users or groups to a Kubernetes RBAC role. This is required when custom OIDC is configured. Refer to the following guides for more information: <br />- [Create Role Bindings](/clusters/cluster-management/cluster-rbac/#create-role-bindings) <br /> - <VersionedLink text="Palette eXtended Kubernetes (PXK)" url="/integrations/packs/?pack=kubernetes&tab=custom" /> | 

_partials/clusters/aws/_aws-account-setup-validate.mdx

@@ -0,0 +1,12 @@
+---
+partial_category: clusters-aws-account-setup
+partial_name: aws-account-setup-validate
+---
+
+1. Log in to {props.edition} as a tenant admin.
+
+2. From the left main menu, select **Tenant Settings**.
+
+3. From the **Tenant Settings Menu**, select **Cloud Accounts**.
+
+4. Verify that your AWS account appears in the **AWS** section.

_partials/clusters/aws/_aws-dynamic-credentials-enablement-1.mdx

@@ -0,0 +1,40 @@
+---
+partial_category: clusters-aws-account-setup
+partial_name: aws-dynamic-credentials-enablement-1
+---
+
+1. Log in to [Palette](https://console.spectrocloud.com) or Palette VerteX as a tenant admin.
+
+2. From the left main menu, select **Tenant Settings**.
+
+3. From the **Tenant Settings** menu, select **Cloud Accounts**.
+
+4. Locate the **AWS** section and select **Add AWS Account**.
+
+5. Fill out the following information.
+
+   | **Palette Parameter**      | **Description**                                                                                     |
+   | -------------------------- | --------------------------------------------------------------------------------------------------- |
+   | **Account Name**           | Enter a custom account name. The account name must be unique within the tenant scope.               |
+   | **Description (Optional)** | Enter a description for the cloud account.                                                          |
+   | **Partition**              | Select **{props.partition}**.                                                                                     |
+   | **STS**                    | Select **STS** to authenticate your AWS account using STS credentials and reveal the **ARN** field. |
+
+6. When you select **STS**, the right side of the wizard populates with details on how to create an IAM role for
+   Palette. Log in to your AWS account and begin the IAM role creation process by navigating to **IAM > Roles > Create
+   role**. The following table expands on the information provided by the wizard.
+
+   | **AWS Parameter**        | **Description**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+   | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+   | **Trusted entity type**  | Select **AWS account**. In the **An AWS account** section, select **Another AWS account**.                                                                                                                                                                                                                                                                                                                                                                                                         |
+   | **Account ID**           | Copy the **Account ID** displayed on the Palette wizard. If using a self-hosted instance, this is the same AWS account that you configured for your Palette or Palette VerteX instance to enable STS. Refer to the appropriate [Enable Adding AWS Accounts Using STS - Palette](/enterprise-version/system-management/configure-aws-sts-account/) or [Enable Adding AWS Accounts Using STS - VerteX](/vertex/system-management/configure-aws-sts-account/) guide for more information. |
+   | **Require external ID**  | In the **An AWS account** section, below **Options**, select **Require External ID**.                                                                                                                                                                                                                                                                                                                                                                                                              |
+   | **External ID**          | Copy the **External ID** displayed on the Palette wizard. This ID is generated by Palette and is different for each tenant.                                                                                                                                                                                                                                                                                                                                                              |
+   | **Permissions policies** | Search for and select the [required IAM policies](/clusters/public-cloud/aws/required-iam-policies/): **PaletteControllerPolicy**, **PaletteControlPlanePolicy**, **PaletteDeploymentPolicy**, and **PaletteNodesPolicy**. If deploying EKS clusters, add the **PaletteControllersEKSPolicy** as well.                                                                                                                                                                                                                      |
+   | **Role name**            | In the **Role details** section, enter `SpectroCloudRole` for the **Role name**.                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+7. Your new role appears in the **Roles** list. Locate and select the new role. In the **Summary** section, copy the
+   Amazon Resource Name (**ARN**) for the role.
+
+8. In Palette, paste the role ARN into the **ARN** field.
+