快速入门：将资源从 Azure Kubernetes 舰队管理器（舰队）中心群集传播到成员群集

1. 使用 kubectl create namespace 命令创建要放置在成员群集上的命名空间。 以下示例创建名为 my-namespace 的命名空间：

   kubectl create namespace my-namespace
   

2. 在中心群集中创建 ClusterResourcePlacement API 对象，以将命名空间传播到成员群集，然后使用 kubectl apply -f 命令部署该命名空间。 以下示例 ClusterResourcePlacement 创建名为 crp 的对象，并使用具有 PickAll 放置策略的 my-namespace 命名空间将命名空间传播到所有成员群集：

   kubectl apply -f - <<EOF
   apiVersion: placement.kubernetes-fleet.io/v1
   kind: ClusterResourcePlacement
   metadata:
     name: crp
   spec:
     resourceSelectors:
       - group: ""
         kind: Namespace
         version: v1          
         name: my-namespace
     policy:
       placementType: PickAll
   EOF
   

3. 使用 kubectl get clusterresourceplacement 命令检查资源传播的进度。 以下示例检查名为 crp 的 ClusterResourcePlacement 对象的状态：

   kubectl get clusterresourceplacement crp
   

   输出应类似于以下示例输出：

   NAME   GEN   SCHEDULED   SCHEDULEDGEN   APPLIED   APPLIEDGEN   AGE
   crp    2     True        2              True      2            10s
   

4. 使用 kubectl describe crp 命令查看 crp 对象的详细信息。 以下示例介绍名为 crp 的 ClusterResourcePlacement 对象：

   kubectl describe clusterresourceplacement crp
   

   输出应类似于以下示例输出：

   Name:         crp
   Namespace:    
   Labels:       <none>
   Annotations:  <none>
   API Version:  placement.kubernetes-fleet.io/v1
   Kind:         ClusterResourcePlacement
   Metadata:
     Creation Timestamp:  2024-04-01T18:55:31Z
     Finalizers:
       kubernetes-fleet.io/crp-cleanup
       kubernetes-fleet.io/scheduler-cleanup
     Generation:        2
     Resource Version:  6949
     UID:               815b1d81-61ae-4fb1-a2b1-06794be3f986
   Spec:
     Policy:
       Placement Type:  PickAll
     Resource Selectors:
       Group:                 
       Kind:                  Namespace
       Name:                  my-namespace
       Version:               v1
     Revision History Limit:  10
     Strategy:
       Type:  RollingUpdate
   Status:
     Conditions:
       Last Transition Time:   2024-04-01T18:55:31Z
       Message:                found all the clusters needed as specified by the scheduling policy
       Observed Generation:    2
       Reason:                 SchedulingPolicyFulfilled
       Status:                 True
       Type:                   ClusterResourcePlacementScheduled
       Last Transition Time:   2024-04-01T18:55:36Z
       Message:                All 3 cluster(s) are synchronized to the latest resources on the hub cluster
       Observed Generation:    2
       Reason:                 SynchronizeSucceeded
       Status:                 True
       Type:                   ClusterResourcePlacementSynchronized
       Last Transition Time:   2024-04-01T18:55:36Z
       Message:                Successfully applied resources to 3 member clusters
       Observed Generation:    2
       Reason:                 ApplySucceeded
       Status:                 True
       Type:                   ClusterResourcePlacementApplied
     Observed Resource Index:  0
     Placement Statuses:
       Cluster Name:  membercluster1
       Conditions:
         Last Transition Time:  2024-04-01T18:55:31Z
         Message:               Successfully scheduled resources for placement in membercluster1 (affinity score: 0, topology spread score: 0): picked by scheduling policy
         Observed Generation:   2
         Reason:                ScheduleSucceeded
         Status:                True
         Type:                  ResourceScheduled
         Last Transition Time:  2024-04-01T18:55:36Z
         Message:               Successfully Synchronized work(s) for placement
         Observed Generation:   2
         Reason:                WorkSynchronizeSucceeded
         Status:                True
         Type:                  WorkSynchronized
         Last Transition Time:  2024-04-01T18:55:36Z
         Message:               Successfully applied resources
         Observed Generation:   2
         Reason:                ApplySucceeded
         Status:                True
         Type:                  ResourceApplied
       Cluster Name:            membercluster2
       Conditions:
         Last Transition Time:  2024-04-01T18:55:31Z
         Message:               Successfully scheduled resources for placement in membercluster2 (affinity score: 0, topology spread score: 0): picked by scheduling policy
         Observed Generation:   2
         Reason:                ScheduleSucceeded
         Status:                True
         Type:                  ResourceScheduled
         Last Transition Time:  2024-04-01T18:55:36Z
         Message:               Successfully Synchronized work(s) for placement
         Observed Generation:   2
         Reason:                WorkSynchronizeSucceeded
         Status:                True
         Type:                  WorkSynchronized
         Last Transition Time:  2024-04-01T18:55:36Z
         Message:               Successfully applied resources
         Observed Generation:   2
         Reason:                ApplySucceeded
         Status:                True
         Type:                  ResourceApplied
       Cluster Name:            membercluster3
       Conditions:
         Last Transition Time:  2024-04-01T18:55:31Z
         Message:               Successfully scheduled resources for placement in membercluster3 (affinity score: 0, topology spread score: 0): picked by scheduling policy
         Observed Generation:   2
         Reason:                ScheduleSucceeded
         Status:                True
         Type:                  ResourceScheduled
         Last Transition Time:  2024-04-01T18:55:36Z
         Message:               Successfully Synchronized work(s) for placement
         Observed Generation:   2
         Reason:                WorkSynchronizeSucceeded
         Status:                True
         Type:                  WorkSynchronized
         Last Transition Time:  2024-04-01T18:55:36Z
         Message:               Successfully applied resources
         Observed Generation:   2
         Reason:                ApplySucceeded
         Status:                True
         Type:                  ResourceApplied
     Selected Resources:
       Kind:     Namespace
       Name:     my-namespace
       Version:  v1
   Events:
     Type    Reason                     Age   From                                   Message
     ----    ------                     ----  ----                                   -------
     Normal  PlacementScheduleSuccess   108s  cluster-resource-placement-controller  Successfully scheduled the placement
     Normal  PlacementSyncSuccess       103s  cluster-resource-placement-controller  Successfully synchronized the placement
     Normal  PlacementRolloutCompleted  103s  cluster-resource-placement-controller  Resources have been applied to the selected clusters
   

1. 在 Azure 门户中，导航到舰队资源。

2. 在服务菜单中的“舰队资源”下，选择资源放置>创建。

3. 将占位符值替换为以下 YAML，然后选择“添加”。

   apiVersion: placement.kubernetes-fleet.io/v1
   kind: ClusterResourcePlacement
   metadata:
     name: crp
   spec:
     resourceSelectors:
       - group: ""
         kind: Namespace
         version: v1          
         name: my-namespace
     policy:
       placementType: PickAll
   

4. 验证是否已成功创建群集资源放置。

   

5. 要查看有关单个群集资源放置的更多详细信息，请从列表中选择它。

   

6. 可以使用各个选项卡查看有关群集资源放置快照、绑定、工作和计划策略快照的其他详细信息。 例如，选择“群集资源快照”选项卡。

   

如果不再需要使用 ClusterResourcePlacement 对象，可以使用 kubectl delete 命令将其删除。 以下示例删除名为 crp 的 ClusterResourcePlacement 对象：

kubectl delete clusterresourceplacement crp

如果不再想使用群集资源放置，可以从 Azure 门户将其删除：

1. 在服务菜单中的“舰队资源”下，选择“资源放置”。
2. 选择要删除的群集资源放置对象，然后选择“删除”。
3. 在“删除”选项卡上，验证是否选择了正确的对象。 准备就绪后，选择确认删除>删除。