Usar o posicionamento de recursos de cluster do Gerenciador de Frotas do Kubernetes do Azure para implantar cargas de trabalho em vários clusters

1. Crie um namespace para atribuir aos clusters membros:

kubectl create namespace my-namespace

2. Crie um objeto ClusterResourcePlacement e aplique-o ao cluster do hub do Gerenciador de frotas. No exemplo a seguir, um ClusterResourcePlacement nomeado distribute-my-namespace é usado para implantar um namespace my-namespace em todos os clusters de membros, utilizando a política de posicionamento PickAll.

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

Aplique isso ao cluster do hub do Fleet Manager emitindo kubectl apply -f distribute-my-namespace.yaml, usando o nome do arquivo que você criou no lugar de distribute-my-namespace.yaml.

3. Verifique o progresso da propagação de recursos:

kubectl get clusterresourceplacement distribute-my-namespace

Seu resultado deve ser semelhante ao seguinte exemplo:

NAME                       GEN   SCHEDULED   SCHEDULEDGEN   APPLIED   APPLIEDGEN   AGE
distribute-my-namespace    2     True        2              True      2            10s

4. Exiba os detalhes do objeto de posicionamento:

kubectl describe clusterresourceplacement distribute-my-namespace

Seu resultado deve ser semelhante ao seguinte exemplo:

Name:         distribute-my-namespace
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. No portal do Azure, acesse o recurso do Fleet Manager.

2. No menu de serviço, em Recursos da Frota, selecione Colocações de recursos>Criar.

3. Substitua os valores de espaço reservado com o YAML a seguir e selecione Adicionar.

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

4. Verifique se o posicionamento do recurso do cluster foi criado com sucesso.

   

5. Para ver mais detalhes sobre a colocação de um recurso de cluster individual, selecione-a na lista.

   

6. Você pode exibir detalhes adicionais sobre instantâneos, associações, trabalhos e instantâneos da política de agendamento do posicionamento de recursos do cluster usando as guias individuais. Por exemplo, selecione a guia Instantâneos de recursos do cluster.

   

Caso não queira mais usar o objeto ClusterResourcePlacement, poderá excluí-lo usando o comando kubectl delete. O exemplo a seguir exclui o objeto ClusterResourcePlacement chamado distribute-my-namespace:

kubectl delete clusterresourceplacement distribute-my-namespace

Caso não queira mais usar a colocação de recurso do cluster, poderá excluí-la do portal do Azure:

1. No menu de serviço, em Recursos da Frota, selecione Colocações de recursos.
2. Selecione os objetos de colocação do recurso de cluster que deseja excluir e selecione Excluir.
3. No guia Excluir, verifique se você escolheu os objetos corretos. Quando tudo estiver pronto, selecione Confirmar exclusão>Excluir.