Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-5200

Document the usecase where tolerations need to be added to Placement object when using ApplicationSets

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • No

      Description of problem:

      when using ApplicationSet ClusterDecisionResource generator
      where might be a situation where the Placement needs to be modified to tolerate temporary disconnects of the Managed-Cluster

      Goal is to better handle Cluster-Offline events also the ArgoCD-Cluster Secret might be deleted and you will get those errors:

      time="2023-04-26T12:08:52Z" level=warning msg="unmatched cluster in ArgoCD" clusterName=cluster1
The Placement/PlacementDecision that your ApplicationSet should not be the same as the one GitOpsCluster is using.
So that the Application can failed over to cluster2
I am hoping that with this setup:
Application (for cluster2) will get deployed successfully on cluster2 after the failed over
Application (for cluster1) will be under deletion (but not removed yet) until cluster1 comes back online so it can reach to cluster1 and cleanup all the resources.

      Solution is to add:

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

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

      3. ...

      Actual results:

      Expected results:

      Additional info:

              mdockery@redhat.com Mikela Jackson
              rhn-support-cstark Christian Stark
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: