GitOps Configuration

The 'GitOps Configuration' page appears only if the super-admin has enabled 'Allow changing git repository for application' in .

Introduction

This configuration is an extension of the settings present in of Devtron. Therefore, make sure you read it before making any changes to your app configuration.

The application-level GitOps configuration offers the flexibility to add a custom Git repo (as opposed to Devtron auto-creating a repo for your application).

Adding Custom Git Repo for GitOps

Who Can Perform This Action?

Users need to have or above (along with access to the environment and application) to configure user-defined Git repo.

For Devtron Apps

Go to Applications → Devtron Apps (tab) → (choose your app) → App Configuration (tab) → GitOps Configuration.
Figure 1: App-level GitOps Config
Assuming a GitOps repo was not added to your application earlier, you get 2 options:
- Auto-create repository - Select this option if you wish to proceed with the default behavior. It will create a repository automatically, named after your application with a prefix. Thus saving you the trouble of creating one manually.
- Commit manifests to a desired repository - Select this option if you wish to add a custom repo that is already created with your . Enter its link in the Git Repo URL field.
Figure 2: Repo Creation

GitOps repositories, whether auto-created by Devtron or added manually, are immutable. This means they cannot be modified after creation. The same is true if you have an existing CD pipeline that uses/used GitOps for deployment.

Click Save.

For Helm Apps

Click Configure & Deploy.
After you enter the App Name, Project, and Environment; an option to choose the deployment approach (i.e., Helm or GitOps) would appear. Select GitOps.