docs: Cluster Templates - Tech Preview Exit (#8957)

* Removing tech preview from cluster templates; adding to release notes

* Update README.md

* Updating image w/o TP banner

* Optimised images with calibre/image-actions

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: achuribooks

README.md

@@ -511,6 +511,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
 
@@ -519,6 +529,8 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
+#### Info
+
 ```mdx
 :::info
 
@@ -527,6 +539,8 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
+#### Tip
+
 ```mdx
 :::tip
 
@@ -535,6 +549,8 @@ Some **content** with _Markdown_ `syntax`.
 :::
 ```
 
+#### Danger
+
 ```mdx
 :::danger
 
@@ -543,6 +559,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
 
@@ -551,6 +576,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
 
@@ -559,12 +600,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/cluster-templates/_profile-vs-template.mdx

@@ -3,17 +3,9 @@ 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.
-
-:::
-
 <Tabs>
 
 <TabItem value="profiles" label="Cluster Profiles">
@@ -36,8 +28,6 @@ or a single <VersionedLink text="cluster template" url="/cluster-templates" />.
 
 <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/self-hosted/feature-flags/_feature-flags-intro.mdx

@@ -17,7 +17,6 @@ The following table lists all available feature flags and their supported platfo
 | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-----------------: | :------------------------: |
 | **AwsSecretPartition** | Configure [AWS Secret Cloud](https://aws.amazon.com/federal/secret-cloud/) accounts and deploy EKS clusters in AWS Secret cloud. Refer to our <VersionedLink text="Register and Manage AWS Accounts" url="/clusters/public-cloud/aws/add-aws-accounts#aws-secret-cloud-account-us" /> guide for more information.                                                                                                                                                         |         :x:         |     :white_check_mark:     |
 | **AzureUSSecretCloud** | Configure [Azure Government Secret](https://azure.microsoft.com/en-us/explore/global-infrastructure/government/national-security) cloud accounts and deploy Azure IaaS clusters in Azure Government Secret cloud.                                                                                                                                                                                                                                     |         :x:         |     :white_check_mark:     |
-| **ClusterTemplate**    | Create reusable blueprints that reference <VersionedLink text="cluster profiles" url="/profiles/cluster-profiles/" /> and <VersionedLink text="policies" url="/cluster-templates/create-cluster-template-policies/" />, allowing you to declaratively define and manage the software and governance stack for a fleet of clusters. Refer to our <VersionedLink text="Cluster Templates" url="/cluster-templates/" /> guide for more information. | :white_check_mark:  |     :white_check_mark:     |
 | **LxdMaas**            | Spawn multiple control plane nodes as LXD VMs and consolidate them on MAAS-managed servers while your worker nodes run on bare metal devices. Refer to our <VersionedLink text="Create and Manage MAAS Clusters Using LXD VMs" url="/clusters/data-center/maas/create-manage-maas-lxd-clusters/" /> guide for more information.                                                                                                                                            | :white_check_mark:  |     :white_check_mark:     |
 
 :::warning

docs/docs-content/cluster-templates/cluster-templates.md

@@ -10,10 +10,6 @@ sidebar_custom_props:
 tags: ["cluster templates", "templates", "policies"]
 ---
 
-:::preview
-
-:::
-
 Cluster templates are reusable blueprints that define and enforce the desired state and lifecycle of clusters deployed
 with Palette or [Palette VerteX](../vertex/vertex.md).
 

docs/docs-content/cluster-templates/create-cluster-template-policies/create-cluster-template-policies.md

@@ -7,10 +7,6 @@ sidebar_position: 0
 tags: ["cluster templates", "policies"]
 ---
 
-:::preview
-
-:::
-
 Policies are an integral part of cluster templates. While cluster profiles define the infrastructure and software stack
 for your clusters, cluster template policies are modular, reusable definitions that define how the cluster operates as
 well as its lifecycle. Policies are linked rather than embedded within cluster templates, allowing you to manage

docs/docs-content/cluster-templates/create-cluster-template-policies/maintenance-policy.md

@@ -7,10 +7,6 @@ sidebar_position: 10
 tags: ["cluster templates", "policies"]
 ---
 
-:::preview
-
-:::
-
 A maintenance policy is a required component for [cluster templates](../cluster-templates.md). Maintenance policies
 determine when and how upgrades are executed on the cluster. Since clusters can be provisioned across multiple regions
 and time zones, upgrades are executed based on Coordinated Universal Time (UTC).

docs/docs-content/cluster-templates/create-cluster-templates.md

@@ -7,10 +7,6 @@ sidebar_position: 10
 tags: ["cluster templates"]
 ---
 
-:::preview
-
-:::
-
 [Cluster templates](./cluster-templates.md) allow you to define and enforce the software and governance stack for a
 fleet of clusters. By referencing [cluster profiles](../profiles/cluster-profiles/cluster-profiles.md) and operational
 [policies](./create-cluster-template-policies/create-cluster-template-policies.md), all while leveraging

docs/docs-content/cluster-templates/delete-cluster-templates.md

@@ -7,10 +7,6 @@ sidebar_position: 30
 tags: ["cluster templates"]
 ---
 
-:::preview
-
-:::
-
 To delete a cluster template that is attached to a cluster, you must first delete the cluster and then delete the
 template previously attached to the cluster. You cannot delete a cluster template that is linked to a cluster.
 

docs/docs-content/cluster-templates/modify-cluster-templates.md

@@ -9,10 +9,6 @@ toc_max_heading_level: 5
 tags: ["cluster templates"]
 ---
 
-:::preview
-
-:::
-
 [Cluster templates](./cluster-templates.md) use [cluster profiles](../profiles/cluster-profiles/cluster-profiles.md) and
 cluster [template policies](./create-cluster-template-policies/create-cluster-template-policies.md) to declaratively
 define and manage the software stack and lifecycle of clusters deployed with Palette. Since cluster templates are

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

@@ -40,6 +40,14 @@ tags: ["release-notes"]
 
 #### Features
 
+- [Cluster templates](../cluster-templates/cluster-templates.md) provide a new way to enforce consistent configurations
+  and prevent drift across multiple clusters. With cluster templates, you define and enforce the desired state and
+  lifecycle of clusters by combining [cluster profiles](../profiles/cluster-profiles/cluster-profiles.md) with
+  operational [policies](../cluster-templates/create-cluster-template-policies/create-cluster-template-policies.md) into
+  a single, reusable governance blueprint, allowing you to deploy, manage, and upgrade a synchronized fleet of clusters
+  with minimal effort. Refer to our [Cluster Templates](../cluster-templates/cluster-templates.md) guide for more
+  information.
+
 #### Improvements
 
 #### Deprecations and Removals