You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-multicluster/4322-cluster-inventory/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -566,9 +566,9 @@ using a secret if possible. Here are the three approaches:
566
566
567
567
#### Pull Model with Work API
568
568
The ClusterInventory Consumer can leverage the [Work API](https://multicluster.sigs.k8s.io/concepts/work-api/) so that
569
-
the work API agent on the Member Cluster can *pull* the necessary objects from the management cluster where the ClusterInventory
569
+
the work API agent on the Member Cluster can *pull* the necessary objects from the hub cluster where the ClusterInventory
570
570
Consumer operates to the Member Cluster. This approach allows the Cluster Manager to manage the RBAC for each Consumer on the
571
-
management cluster, ensuring that their access is restricted to the corresponding namespaces of the ClusterProfile objects.
571
+
hub cluster, ensuring that their access is restricted to the corresponding namespaces of the ClusterProfile objects.
572
572
573
573
#### Push Model with Identity Federation (Recommended)
574
574
The ClusterInventory consumer can utilize identity federation mechanisms, such as [Azure Workload Identity Federation](https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation)
0 commit comments