Skip to main content
Version: main

GitOps Automation Configuration

Weave GitOps has a key concept which is the "GitOps Automation". This is the configuration that defines the flow that happens when an update happens in Git. This flow reconciles the workload into the target.

What is the GitOps Automation Configuration?#

The GitOps Automation configuration consists of two types of configuration: apps and clusters. Fundamentally, GitOps is connecting apps with clusters by automatically deploying the app into the cluster.

Where does it live?#

The configuration is stored in the repository specified in gitops install. The application manifests can be stored in the same repository as the configuration or a separate repository.

What files are there#

The .weave-gitops folder contains the following structure:

.weave-gitopsโ”œโ”€โ”€ appsโ”‚   โ””โ”€โ”€ <app name>โ”‚       โ”œโ”€โ”€ app.yamlโ”‚       โ”œโ”€โ”€ kustomization.yamlโ”‚       โ”œโ”€โ”€ <app name>-gitops-deploy.yamlโ”‚       โ””โ”€โ”€ <app name>-gitops-source.yamlโ””โ”€โ”€ clusters    โ””โ”€โ”€ <cluster name>        โ”œโ”€โ”€ system        โ”‚   โ”œโ”€โ”€ flux-source-resource.yaml        โ”‚   โ”œโ”€โ”€ flux-system-kustomization-resource.yaml        โ”‚   โ”œโ”€โ”€ flux-user-kustomization-resource.yaml        โ”‚   โ”œโ”€โ”€ gitops-runtime.yaml        โ”‚   โ”œโ”€โ”€ wego-app.yaml        โ”‚   โ””โ”€โ”€ wego-system.yaml        โ””โ”€โ”€ user            โ””โ”€โ”€ kustomization.yaml


The app.yaml looks like this:

---apiVersion: Applicationmetadata:  labels: wego-52cdbd4b6d1a20a934f101708a93cf10  name: <app name>  namespace: wego-systemspec:  branch: main  config_url: ssh://  deployment_type: kustomize  path: ./  source_type: git  url: ssh://<yr-org-goes-here>/podinfo-deploy.git

It defines:

  • the name of the application (name)
  • the namespace of the application (namespace)
  • the git URL location of the repository, or URL of the helm repository for a helm chart (url)
  • the path and branch containing the application manifests within the repository (path, branch)
  • the git URL location of the configuration repository (config_url)
  • whether the application will be read from a helm repository or a git repository (source_type)
  • how the application will be deployed -- via kustomize or a helm release (deployment_type)


The kustomization.yaml file defines the set of resources that will be managed via GitOps for the application.

apiVersion: Kustomizationmetadata:  name: <app name>  namespace: wego-systemresources:- app.yaml- <app name>-gitops-deploy.yaml- <app name>-gitops-source.yaml

The content of each file mentioned in the resources section is synchronized with the cluster by flux. The kustomization.yaml file itself is associated with the cluster via a reference to the app directory in the user kustomization file for the cluster (.weave-gitops/clusters/<cluster name>/user/kustomization.yaml).

<app name>-gitops-source.yaml#

This file defines how the application will be read into the system. Current options are GitRepository and HelmRepository:

apiVersion: GitRepositorymetadata:  name: <app name>  namespace: wego-systemspec:  ignore: |-    .weave-gitops/    .git/    .gitignore    .gitmodules    .gitattributes    *.jpg    *.jpeg    *.gif    *.png    *.wmv    *.flv    *.tar.gz    *.zip    .github/    .circleci/    .travis.yml    .gitlab-ci.yml    appveyor.yml    .drone.yml    cloudbuild.yaml    codeship-services.yml    codeship-steps.yml    **/.goreleaser.yml    **/.sops.yaml    **/.flux.yaml  interval: 30s  ref:    branch: main  url:<yr-org-goes-here>/podinfo-deploy.git

<app name>-gitops-deploy.yaml#

This file defines the flux runtime flow to deploy the application into a specific target. For example, by default this uses the flux kustomize support to deploy your application manifests into the cluster. Other options include managing helm charts.

---apiVersion: Kustomizationmetadata:  name: <app name>  namespace: wego-systemspec:  interval: 1m0s  path: ./  prune: true  sourceRef:    kind: GitRepository    name: <app name>