Skip to content

Get ArgoCD to manage your Application

When migrating an application's deployment to be managed by ArgoCD use the following checklist to verify your process.

  • Ensure your application manifests can be built using Kustomize.
    • Specify your apiVersion in your manifests with the apigroup included (e.g. for Deployments use apps.openshift.io/v1 instead of just v1)
  • If using secrets, make sure to include the .sops.yaml file in your repository.
    • See here for more info.
  • Create the role granting access to namespace.
    • See here for more info.
    • This role should be tracked in your application manifest repository.
    • If adding this role as part of the PR below, make sure not to include it in the kustomization.yaml file so that ArgoCD does not deploy it (due to lack of permissions)

The following items require a PR to the aicoe-cd repository, and require an aicoe-sre team member to merge/deploy changes:

  • Ensure the application repository is added in the repository file in repositories.
  • Ensure that all OCP resources that will be managed by ArgoCD on this cluster are included in the inclusions list in resource.inclusions.
    • See here for more info.
  • Create the ArgoCD Application manifest
    • See here for more info.

The following require an aicoe-sre team member to make the changes:

  • Ensure your namespace exists in your cluster's spec see here for details.
  • If you are switching between ArgoCD managed namespaces, and that namespace was deleted in OCP, then ensure it's also removed from your cluster's credentials found here clusters.