GitOps configuration with Helm charts

CloudBees CD/RO features options to configure GitOps repositories during helm installation and upgrade. These options allow devops administrators to:

Create repository plugin configuration(s) based on supplied credentials
Create source code synchronization object(s) (scmSync) for supplied repositories
Attach a polling trigger to the scmSync object

You can currently configure only one repository during installation or upgrade.

Creating a values configuration for GitOps

GitOps support on CloudBees CD/RO can be configured using the following values:

gitops:
  enabled: false
  repo:
# Either specify the secret where the gitToken is stored under
# the 'CBF_GIT_TOKEN' key (recommended for production) or specify
  gitToken:
  existingSecret:

Example configuration

In the following example, a GitOps repository gitopsdemo is created containing the configuration for a CloudBees CD/RO instance.

Create the secret to be used in your GitOps con:figure-caption:

kubectl create secret generic my-gitops-token \
--from-literal=CBF_GIT_TOKEN='ghp_rdfdffdffdfdummmytoken' \
 -n <namespace>

Append the GitOps configuration to your custom configuration (such as myvalues.yaml):

gitops:
  enabled: true
  repo: https://github.com/flow-on-kubernetes/gitopsdemo.git
  existingSecret: my-gitops-token

Once configured, the GitOps project can be accessed from Projects page.