Merge branch 'master' of github.com:spectrocloud/librarium into relea…

…se-4-2

docs/docs-content/clusters/public-cloud/aws/eks.md

@@ -88,7 +88,7 @@ Use the following steps to deploy an EKS cluster on AWS.
   |**SSH Key Pair Name** | Choose the SSH key pair for the region you selected. SSH key pairs must be pre-configured in your AWS environment. This is called an EC2 Key Pair in AWS. The key you select is inserted into the provisioned VMs.|
   |**Cluster Endpoint Access**| This setting provides access to the Kubernetes API endpoint. Select **Private**, **Public** or **Private & Public**. For more information, refer to the [Amazon EKS cluster endpoint access control](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) reference guide.|
   |**Public Access CIDRs** |This setting controls which IP address CIDR ranges can access the cluster. To fully allow unrestricted network access, enter `0.0.0.0/0` in the field. For more information, refer to the [Amazon EKS cluster endpoint access control](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) reference guide.|
-  |**Private Access CIDRs** |This setting controls which private IP address CIDR ranges can access the cluster. Private CIDRs provide a way to specify private, self-hosted, and air-gapped networks or Private Cloud Gateway (PCG) that may be located in other VPCs connected to the VPC hosting the cluster endpoint.<br /><br />To restrict network access, enter the IP address CIDR range that will provide access to the cluster. Although `0.0.0.0/0` is pre-populated in this field, only IPs that can reach the private endpoint are those within the VPC or any other connected VPCs. For example, while using `0.0.0.0/0` would allow traffic throughout the VPC and all peered VPCs, specifying the VPC CIDR `10.0.0.0/16` would limit traffic to an individual VPC. For more information, refer to the [Amazon EKS cluster endpoint access control](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) reference guide.|
+  |**Private Access CIDRs** |This setting controls which private IP address CIDR ranges can access the cluster. Private CIDRs provide a way to specify private, self-hosted, and air-gapped networks or Private Cloud Gateway (PCG) that may be located in other VPCs connected to the VPC hosting the cluster endpoint.<br /><br />To restrict network access, replace the pre-populated 0.0.0.0/0 with the IP address CIDR range that should be allowed access to the cluster endpoint. Only the IP addresses that are within the specified VPC CIDR range - and any other connected VPCs - will be able to reach the private endpoint. For example, while using `0.0.0.0/0` would allow traffic throughout the VPC and all peered VPCs, specifying the VPC CIDR `10.0.0.0/16` would limit traffic to an individual VPC. For more information, refer to the [Amazon EKS cluster endpoint access control](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) reference guide.|
   |**Enable Encryption**| Use this option for secrets encryption. You must have an existing AWS Key Management Service (KMS) key you can use. Toggle the **Enable encryption** option and use the **drop-down Menu** in the **ARN** field to select the KMS key ARN.<br /><br />If you do not have a KMS key and want to create one to use this option, review [Enable Secrets Encryption for EKS Cluster](enable-secrets-encryption-kms-key.md). Once your KMS key is created, return to this Cluster Config step to enable secrets encryption and specify the KMS key ARN. |
 
   :::caution

docs/docs-content/profiles/cluster-profiles/cluster-profiles.md

@@ -23,7 +23,7 @@ The diagram below illustrates the components of these profile types and how you
 
 ## Profile Layers
 
-Each cluster profile layer provides a specific functionality. Profile layers can be packs, Helm Charts, or custom manifests, as described in the table.
+Each cluster profile layer provides a specific functionality. Profile layers can be packs, Helm Charts, or custom manifests, as described in the table. Adding a pack multiple times to the same cluster profile is possible. To learn more about this scenario, review [Deploy Same Pack to Multiple Layers](../cluster-profiles/create-cluster-profiles/duplicate-pack-in-profile.md).
 
 | **Layer** | **Description** |
 |-----------|---------------------------|

docs/docs-content/profiles/cluster-profiles/create-cluster-profiles/create-addon-profile/create-helm-addon.md

@@ -9,7 +9,7 @@ tags: ["profiles", "cluster profiles", "helm", "add-on"]
 
 
 
-You can extend the list of integrations by adding Helm charts from a public or private registries to your cluster profile. Use the following steps to create an add-on cluster profile that adds a Helm chart layer.
+You can extend the list of integrations by adding Helm charts from a public or private registry to your cluster profile. Use the following steps to create a cluster profile by adding layers using Helm charts.
 
 ## Prerequisites
 

docs/docs-content/profiles/cluster-profiles/create-cluster-profiles/create-addon-profile/create-manifest-addon.md

@@ -9,7 +9,8 @@ tags: ["profiles", "cluster profiles", "manifest", "add-on"]
 
 
 
-You can extend the list of integrations by adding custom manifests to your cluster profile. Use the following steps to create a cluster profile that adds a custom manifest layer.
+You can extend the list of integrations by adding custom manifests to your cluster profile. Use the following steps to create a cluster profile by adding layers using manifests.
+
 
 ## Prerequisites
 

docs/docs-content/profiles/cluster-profiles/create-cluster-profiles/create-addon-profile/create-pack-addon.md

@@ -9,7 +9,8 @@ tags: ["profiles", "cluster profiles", "pack", "add-on"]
 
 
 
-Use the following steps to create an add-on cluster profile that adds a pack layer.
+Use the following steps to create a cluster profile by adding one or more layers using packs.
+
 
 ## Prerequisites
 

docs/docs-content/profiles/cluster-profiles/create-cluster-profiles/create-infrastructure-profile.md

@@ -8,7 +8,7 @@ tags: ["profiles", "cluster profiles"]
 ---
 
 
-Create an infrastructure profile by adding infrastructure layers composed of an Operating System (OS), Kubernetes, Network, and Storage.
+Create an infrastructure profile by adding layers composed of an Operating System (OS), Kubernetes, Network, and Storage packs.
 
 ## Prerequisites
 

docs/docs-content/profiles/cluster-profiles/create-cluster-profiles/duplicate-pack-in-profile.md

@@ -1,6 +1,6 @@
 ---
-sidebar_label: "Duplicate a Pack in a Profile"
-title: "Duplicate a Pack in a Profile"
+sidebar_label: "Deploy Same Pack to Multiple Layers"
+title: "Deploy Same Pack to Multiple Layers"
 description: "Learn how to deploy the same pack to multiple layers in a Palette cluster profile."
 hide_table_of_contents: false
 sidebar_position: 30
@@ -9,11 +9,11 @@ tags: ["profiles", "cluster profiles"]
 
 
 
-Palette allows you to deploy the same pack to multiple layers, which can be required in certain scenarios where an integration needs to be installed more than once with different configurations. For example, you may need to deploy two instances of the same microservice or application but with different configurations. In this case, you will need to launch the Postgres application twice with different configurations.
+Palette allows you to add a pack multiple times to the same cluster profile, which can be required in certain scenarios where an integration needs to be installed more than once with different configurations. For example, you may need to deploy two instances of the same microservice or application but with different configurations. In this case, you will need to launch the Postgres application twice with different configurations.
 
-::: caution
+:::caution
 
-Depending on the application, you might have to place the duplicate pack in a different namespace, as resource conflicts could arise from the original pack having Kubernetes resources named identical to the one the second pack would create.
+Depending on the application, you might have to place the repeated pack in a different namespace, as resource conflicts could arise from the original pack having Kubernetes resources named identical to the one the second pack would create.
 
 :::
 

docs/docs-content/profiles/cluster-profiles/export-import-cluster-profile.md

@@ -18,11 +18,11 @@ Instead of rebuilding cluster profiles, you can export them in JSON format and t
 
 - [Macros](../../registries-and-packs/pack-constraints.md#pack-macros) used in the profile you want to export must be available in the target environment *before* you import the profile. 
 
-:::caution
+  :::caution
 
-If custom macros are not available in the target environment, create them there before importing the profile. For instructions on macro creation, review [Macro Support](../../clusters/cluster-management/macros.md#create-your-macro).
+  If custom macros are not available in the target environment, create them there before importing the profile. For instructions on macro creation, review [Macro Support](../../clusters/cluster-management/macros.md#create-your-macro).
 
-:::
+  :::
 
 
 ## Export Cluster Profile

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

@@ -14,9 +14,14 @@ You can modify cluster profiles by updating the following:
 
 - Profile layers or pack versions.
 
-You can also create multiple versions of a cluster profile with different pack configurations. For more information, review the [Version a Cluster Profile](version-cluster-profile.md) guide.
+  :::caution
 
-In the event that more than one application in the profile needs the same pack, Palette allows you to deploy the same pack to multiple layers. Check out [Duplicate a Pack in a Profile](../create-cluster-profiles/duplicate-pack-in-profile.md) for more information.
+  If you want to update cluster profiles that have been used to deploy clusters, we recommend creating a *new* profile version, and then upgrade active clusters to the new version. To learn how to version profiles, review [Version a Cluster Profile](version-cluster-profile.md) guide.
+
+  :::
+
+
+In the event that more than one application in the profile needs the same pack, Palette allows you to deploy the same pack to multiple layers. Check out [Deploy Same Pack to Multiple Layers](../create-cluster-profiles/duplicate-pack-in-profile.md) for more information.
 
 The next sections guide you in updating and versioning a profile.
 

docs/docs-content/profiles/cluster-profiles/modify-cluster-profiles/update-cluster-profile.md

@@ -12,6 +12,12 @@ You can update a cluster profile to change the configuration of one or more laye
 
 Cluster profile changes will generate an update notification on all the clusters that are created from the profile. Update notifications include information about all the changes applied to the profile since the initial creation or since the previous update. You can apply cluster updates individually at any time.
 
+:::caution
+
+We do not recommend updating a currently deployed cluster profile version to push out changes. Instead, we recommend creating a *new* profile version, and then upgrade active clusters to the new version. For information on versioning profiles, check out [Version a Cluster Profile](version-cluster-profile.md). 
+
+:::
+
 
 ## Prerequisites