When the ACM UI generates default Placement CRs for Application Lifecycle OpenShift GitOps (Argo CD) integration, the Placement resources should automatically include the unreachable and unavailable tolerations. These tolerations ensure that ManagedClusters experiencing temporary network issues remain selected by the Placement instead of being momentarily excluded.

kind: Placement
...
spec:
...
  tolerations:
    - key: cluster.open-cluster-management.io/unreachable
      operator: Exists
    - key: cluster.open-cluster-management.io/unavailable
      operator: Exists 

Today, the lack of these tolerations causes Argo CD to undesirably undeploy applications whenever a cluster briefly disconnects from the hub, which has resulted in multiple customer incidents. Although ACM GitOps documentation already recommends enabling these tolerations, the UI generated default Placements do not currently include them.

Completing this task will ensures that all default Placements created by the ACM UI both for GitOpsCluster CRs (ACM cluster sync to Argo CD) and ApplicationSet CRs (application deployment) automatically include these tolerations to prevent unnecessary application removal during transient network outages.

Refs: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/gitops/gitops-overview#tolerations-config