6.2. Preparing a parallel Argo CD pipeline for ClusterInstance CRs

Procedure

1. Create YAML files for the parallel Argo project and application:

   1. Create a YAML file that defines the AppProject resource:

      Example ztp-app-project-v2.yaml file

      apiVersion: argoproj.io/v1alpha1
      kind: AppProject
      metadata:
        name: ztp-app-project-v2
        namespace: openshift-gitops
      spec:
        clusterResourceWhitelist:
        - group: hive.openshift.io
          kind: ClusterImageSet
        - group: hive.openshift.io
          kind: ClusterImageSet
        - group: cluster.open-cluster-management.io
          kind: ManagedCluster
        - group: ""
          kind: Namespace
        destinations:
        - namespace: '*'
          server: '*'
        namespaceResourceWhitelist:
        - group: ""
          kind: ConfigMap
        - group: ""
          kind: Namespace
        - group: ""
          kind: Secret
        - group: agent-install.openshift.io
          kind: InfraEnv
        - group: agent-install.openshift.io
          kind: NMStateConfig
        - group: extensions.hive.openshift.io
          kind: AgentClusterInstall
        - group: hive.openshift.io
          kind: ClusterDeployment
        - group: metal3.io
          kind: BareMetalHost
        - group: metal3.io
          kind: HostFirmwareSettings
        - group: agent.open-cluster-management.io
          kind: KlusterletAddonConfig
        - group: cluster.open-cluster-management.io
          kind: ManagedCluster
        - group: siteconfig.open-cluster-management.io
          kind: ClusterInstance 

      1

      
        sourceRepos:
        - '*'

      1

      The ClusterInstance CR manages the siteconfig.open-cluster-management.io object instead of the SiteConfig CR.

   2. Create a YAML file that defines the Application resource:

      Example clusters-v2.yaml file

      apiVersion: argoproj.io/v1alpha1
      kind: Application
      metadata:
        name: clusters-v2
        namespace: openshift-gitops
      spec:
        destination:
          namespace: clusters-sub
          server: https://kubernetes.default.svc
        ignoreDifferences:
        - group: cluster.open-cluster-management.io
          kind: ManagedCluster
          managedFieldsManagers:
          - controller
        project: ztp-app-project-v2 

      1

      
        source:
          path: site-configs-v2 

      2

      
          repoURL: http://infra.5g-deployment.lab:3000/student/ztp-repository.git
          targetRevision: main
        syncPolicy:
          syncOptions:
          - CreateNamespace=true
          - PrunePropagationPolicy=background
          - RespectIgnoreDifferences=true

      1

      The project field must match the name of the AppProject resource created in the previous step.

      2

      The path field must match the root folder in your Git repository that will contain the ClusterInstance CRs and associated resources.

      注意

      By default, auto-sync is enabled. However, synchronization only occurs when you push configuration data for the cluster to the new configuration folder, or in this example, the site-configs-v2/ folder.

2. Create and commit a root folder in your Git repository that will contain the ClusterInstance CRs and associated resources, for example:

   $ mkdir site-configs-v2
   $ touch site-configs-v2/.gitkeep
   $ git commit -s -m “Creates cluster-instance folder”
   $ git push origin main

   • The .gitkeep file is a placeholder to ensure that the empty folder is tracked by Git.

     注意

     You only need to create and commit the root site-configs-v2/ folder during pipeline setup. You will mirror the complete site-configs/ folder structure into site-configs-v2/ during the cluster migration procedure.

3. Apply the AppProject and Application resources to the hub cluster by running the following commands:

   $ oc apply -f ztp-app-project-v2.yaml
   $ oc apply -f clusters-v2.yaml

Verification

1. Verify that the original Argo CD project, ztp-app-project, and the new Argo CD project, ztp-app-project-v2 are present on the hub cluster by running the following command:

   $ oc get appprojects -n openshift-gitops

   Example output

   NAME                 AGE
   default              46h
   policy-app-project   42h
   ztp-app-project      18h
   ztp-app-project-v2    14s

2. Verify that the original Argo CD application, clusters, and the new Argo CD application, clusters-v2 are present on the hub cluster by running the following command:

   $ oc get application.argo -n openshift-gitops

   Example output

   NAME                       SYNC STATUS   HEALTH STATUS
   clusters                   Synced        Healthy
   clusters-v2                Synced        Healthy
   policies                   Synced        Healthy