Merge pull request #275938 from sdesai345/main

Removing preview callout and adding clusterrole yaml to examples

Author: prmerger-automator[bot]

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

@@ -54,7 +54,18 @@ spec:
       name: secret-reader
 ```
 
-This example selects a `ClusterRole` named `secret-reader` from the `rbac.authorization.k8s.io/v1` API group for overriding.
+This example selects a `ClusterRole` named `secret-reader` from the `rbac.authorization.k8s.io/v1` API group, as shown below, for overriding.
+
+```yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+  name: secret-reader
+rules:
+- apiGroups: [""]
+  resources: ["secrets"]
+  verbs: ["get", "watch", "list"]
+```
 
 ## Policy
 
@@ -152,7 +163,18 @@ spec:
             path: /rules/0/verbs/1
 ```
 
-This example removes the verbs "list" and "watch" in the `ClusterRole` named `secret-reader` on clusters with the label `env: prod`.
+This example removes the verbs "list" and "watch" in the `ClusterRole` named `secret-reader` on clusters with the label `env: prod`, as shown below.
+
+```yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+  name: secret-reader
+rules:
+- apiGroups: [""]
+  resources: ["secrets"]
+  verbs: ["get", "watch", "list"]
+```
 
 `jsonPatchOverrides` apply a JSON patch on the selected resources following [RFC 6902](https://datatracker.ietf.org/doc/html/rfc6902).
 

articles/kubernetes-fleet/concepts-choosing-fleet.md

@@ -38,7 +38,7 @@ For more information, see [Create a Kubernetes Fleet resource without a hub clus
 
 ## Kubernetes Fleet resource with hub clusters
 
-A Kubernetes Fleet resource with a hub cluster has an associated AKS-managed cluster, which is used to store the configuration for workload orchestration and layer-4 load balancing.
+A Kubernetes Fleet resource with a hub cluster has an associated AKS-managed cluster, which hosts the open sourced [fleet manager][fleet-github] and [fleet network manager][fleet-networking-github] solution for workload orchestration and layer-4 load balancing.
 
 Upon the creation of a Kubernetes Fleet resource with a hub cluster, a hub AKS cluster is automatically created in the same subscription under a managed resource group that begins with `FL_`. To improve reliability, hub clusters are locked down by denying any user-initiated mutations to the corresponding AKS clusters (under the Fleet-managed resource group `FL_`) and their underlying Azure resources (under the AKS-managed resource group `MC_FL_*`), such as virtual machines (VMs), via Azure deny assignments. Control plane operations, such as changing the hub cluster's configuration through Azure Resource Manager (ARM) or deleting the cluster entirely, are denied. Data plane operations, such as connecting to the hub cluster's Kubernetes API server in order to configure workload orchestration, are not denied.
 
@@ -74,3 +74,7 @@ Now that you understand the different types of Kubernetes fleet resources, see [
 [create-fleet-without-hub]: quickstart-create-fleet-and-members.md?tabs=without-hub-cluster#create-a-fleet-resource
 [create-public-hub-cluster]: quickstart-create-fleet-and-members.md?tabs=with-hub-cluster#public-hub-cluster
 [create-private-hub-cluster]: quickstart-create-fleet-and-members.md?tabs=with-hub-cluster#private-hub-cluster
+
+<!-- LINKS - external -->
+[fleet-github]: https://github.com/Azure/fleet
+[fleet-networking-github]: https://github.com/Azure/fleet-networking

articles/kubernetes-fleet/concepts-resource-propagation.md

@@ -1,5 +1,5 @@
 ---
-title: "Kubernetes resource propagation from hub cluster to member clusters (Preview)"
+title: "Kubernetes resource propagation from hub cluster to member clusters"
 description: This article describes the concept of Kubernetes resource propagation from hub cluster to member clusters.
 ms.date: 03/04/2024
 author: shashankbarsin
@@ -10,7 +10,7 @@ ms.custom:
 ms.topic: conceptual
 ---
 
-# Kubernetes resource propagation from hub cluster to member clusters (Preview)
+# Kubernetes resource propagation from hub cluster to member clusters
 
 This article describes the concept of Kubernetes resource propagation from hub clusters to member clusters using Azure Kubernetes Fleet Manager (Fleet).