Merge pull request #279645 from Nickomang/fleet-crp-portal

Fleet CRP portal

Author: v-regandowner

articles/kubernetes-fleet/cluster-resource-override.md

@@ -178,7 +178,9 @@ rules:
 
 `jsonPatchOverrides` apply a JSON patch on the selected resources following [RFC 6902](https://datatracker.ietf.org/doc/html/rfc6902).
 
-## Apply the cluster resource override
+## Apply the cluster resource placement
+
+### [Azure CLI](#tab/azure-cli)
 
 1. Create a `ClusterResourcePlacement` resource to specify the placement rules for distributing the cluster resource overrides across the cluster infrastructure, as shown in the following example. Make sure you select the appropriate resource.
 
@@ -245,9 +247,52 @@ rules:
           Type:                  Overridden
          ...
     ```
-
+    
     The `ClusterResourcePlacementOverridden` condition indicates whether the resource override was successfully applied to the selected resources in the clusters. Each cluster maintains its own `Applicable Cluster Resource Overrides` list, which contains the cluster resource override snapshot if relevant. Individual status messages for each cluster indicate whether the override rules were successfully applied.
 
+### [Portal](#tab/azure-portal)
+
+1. On the Azure portal overview page for your Fleet resource, in the **Fleet Resources** section, select **Resource placements**.
+
+1. Select **Create**.
+
+1. Create a `ClusterResourcePlacement` resource to specify the placement rules for distributing the cluster resource overrides across the cluster infrastructure, as shown in the following example. Make sure you select the appropriate resource. Replace the default template with the YAML example below, and select **Add**.
+
+    :::image type="content" source="./media/cluster-resource-override/crp-create-inline.png" lightbox="./media/cluster-resource-override/crp-create.png" alt-text="A screenshot of the Azure portal page for creating a resource placement, showing the YAML template with placeholder values.":::
+
+    ```yaml
+    apiVersion: placement.kubernetes-fleet.io/v1beta1
+    kind: ClusterResourcePlacement
+    metadata:
+      name: crp
+    spec:
+      resourceSelectors:
+        - group: rbac.authorization.k8s.io
+          kind: ClusterRole
+          version: v1
+          name: secret-reader
+      policy:
+        placementType: PickAll
+        affinity:
+          clusterAffinity:
+            requiredDuringSchedulingIgnoredDuringExecution:
+              clusterSelectorTerms:
+                - labelSelector:
+                    matchLabels:
+                      env: prod
+    ```
+
+    This example distributes resources across all clusters labeled with `env: prod`. As the changes are implemented, the corresponding `ClusterResourceOverride` configurations will be applied to the designated clusters, triggered by the selection of matching cluster role resource, `secret-reader`.
+
+
+1. Verify that the cluster resource placement is created successfully.
+
+    :::image type="content" source="./media/cluster-resource-override/crp-success-inline.png" lightbox="./media/cluster-resource-override/crp-success.png" alt-text="A screenshot of the Azure portal page for cluster resource placements, showing a successfully created cluster resource placement.":::
+
+1. Verify the cluster resource placement applied to the selected resources by selecting the resource from the list and checking the status.
+
+---
+
 ## Next steps
 
 To learn more about Fleet, see the following resources:

articles/kubernetes-fleet/intelligent-resource-placement.md

@@ -23,6 +23,8 @@ Kubernetes Fleet provides resource placement capability that can make scheduling
 
 [!INCLUDE [preview-callout](./includes/preview/preview-callout.md)]
 
+This article discusses creating cluster resource placements, which can be done via Azure CLI or the Azure portal. For more, see [Propagate resources from a Fleet hub cluster to member clusters](./quickstart-resource-propagation.md).
+
 ## Prerequisites
 
 * Read the [resource propagation conceptual overview](./concepts-resource-propagation.md) to understand the concepts and terminology used in this quickstart.
@@ -225,15 +227,28 @@ spec:
 
 In this example, a cluster would only receive extra weight if it has the label `env=prod`. If it satisfies that label based constraint, then the cluster is given proportional weight based on the amount of total CPU in that member cluster.
 
-
 ## Clean up resources
 
-If you no longer wish to use the `ClusterResourcePlacement` objects created in this article, you can delete them using the `kubectl delete` command. For example:
+### [Azure CLI](#tab/azure-cli)
+
+If you no longer wish to use the `ClusterResourcePlacement` object, you can delete it using the `kubectl delete` command. The following example deletes the `ClusterResourcePlacement` object named `crp`:
 
 ```bash
-kubectl delete clusterresourceplacement <name-of-the-crp-resource>
+kubectl delete clusterresourceplacement crp
 ```
 
+### [Portal](#tab/azure-portal)
+
+If you no longer wish to use your cluster resource placement, you can delete it from the Azure portal:
+
+1. On the Azure portal overview page for your Fleet resource, in the **Fleet Resources** section, select **Resource placements**.
+
+1. Select the cluster resource placement objects you want to delete, then select **Delete**.
+
+1. In the **Delete** tab, verify the correct objects are chosen. Once you're ready, select **Confirm delete** and **Delete**.
+
+---
+
 ## Next steps
 
 To learn more about resource propagation, see the following resources: