Skip to content

Argo CD Operator Release Process

  • VERSION in makefile defines the project version for the bundle.Update this value when you upgrade the version of your project.
  VERSION ?= 0.2.0
  • Ensure that the replaces field in clusterserviceversion(CSV) is set to the version you are planning to release.
  config/manifests/bases/argocd-operator.clusterserviceversion.yaml
  • Ensure that the 'currentCSV' field in operator package is set to the version you are planning to release.
  deploy/olm-catalog/argocd-operator/argocd-operator.package.yaml
  • Build the argocd-operator-util image.
  make util-build
  • Push the argocd-operator-util image to quay.io
  make util-push
  • Copy the SHA digest of utility container image from the above command. Set this value to ArgoCDDefaultExportJobVersion in the defaults file.
  common/defaults.go
  • Build the operator container image. Below command assumes the release version as v0.2.0. Please change the command accordingly.
  make docker-build IMG=quay.io/argoprojlabs/argocd-operator:v0.2.0-rc1
  • Push the operator container image. Below command assumes the release version as v0.2.0. Please change the command accordingly.
  make docker-push IMG=quay.io/argoprojlabs/argocd-operator:v0.2.0-rc1
  • Create the bundle artifacts using the SHA of the operator container image.
  make bundle IMG=quay.io/argoprojlabs/argocd-operator@sha256:d894c0f7510c8f41b48900b52eac94f623885fd409ebf2660793cd921b137bde
  • Create the registry image. Below command assumes the release version as v0.2.0. Please change the command accordingly.
  make registry-build REGISTRY_IMG=quay.io/argoprojlabs/argocd-operator-registry:v0.2.0-rc1
  • Push the registry image. Below command assumes the release version as v0.2.0. Please change the command accordingly.
  make registry-push REGISTRY_IMG=quay.io/argoprojlabs/argocd-operator-registry:v0.2.0-rc1
  • Update the catalog source with the SHA of the operator registry image.
  deploy/catalog_source.yaml

  • Once all testing has been done, from the quay.io user interface, add the actual release tags (e.g. 'v0.2.0') to the argocd-operator and argocd-operator-registry images.

  • Commit and push the changes, then create a PR and get it merged.

  • Go to the argocd operator page and create a new release.

  https://github.com/argoproj-labs/argocd-operator/releases

Steps to create a PR for Kubernetes OperatorHub Community Operators

  • Create a fork of kubernetes community operators.
https://github.com/k8s-operatorhub/community-operators

  • Go to the community-operators/operators/argocd-operator folder

  • Copy the relevant release folder from the actual argocd-operator's 'deploy/olm-catalog/argocd-operator' folder into this folder

  • Edit the argocd-operator.package.yaml file and update the value of the currentCSV field

  • Edit the CSV file in the new release folder, and add a containerImage tag to the metadata section. Copy the value from the image tag already found in the file.

  • Commit and push the changes, then create a PR.

Steps to create a PR for Red Hat Operators

  • Create a fork of redhat community operators.
https://github.com/redhat-openshift-ecosystem/community-operators-prod

  • Go to the 'community-operators-prod/operators/argocd-operator' folder.

  • Copy the relevant release folder from the actual argocd-operator's deploy/olm-catalog/argocd-operator. folder into this folder.

  • Edit the argocd-operator.package.yaml file and update the value of the currentCSV field

  • Edit the CSV file in the new release folder, and add a containerImage tag to the metadata section. Copy the value from the image tag already found in the file.

  • Commit and push the changes, then create a PR.

  • In the argocd-operator repo, synchronize any changes in the release folder under deploy/olm-catalog/argocd-operator on the release branch back to the master branch (ensure the folder is an exact copy of what's on the release branch)

  • Update the VERSION in the Makefile in the argocd-operator repo's master branch to the next version (e.g. from `0.2.0 to 0.3.0)

  • Run make bundle to generate the intial bundle manifests for the next version

  • Commit and push the changes, then create a PR