Gitops

Manage multiple apps across one or more k8s clusters.

Overview

Keeping track of numerous of single-tenanted application deployments can quickly become a handful. Enter Gitops!

The tool has two halves:

Gitops Server - an instance of this gets deployed to each of your kubernetes clusters, listening on changes made to your gitops cluster repo. The server's responsibility is to update the deployments on the cluster it lives on to match the app specifications in the repo.
Gitops CLI - this is a tool that you can use to interact comfortably with your cluster repo. It allows listing all deployed applications, what images they're presently running on, and which clusters they live on. It also provides numerous operations that can be applied to one or more apps at a time, such as bumping to a newer version of an image, or running a particular command across your app cohort.

Currently Kubernetes/Helm is the only supported cluster interface. All app deployments are performed as applications of Helm charts.

So what's a "cluster repo"?

This is a git repository that you set up, where you list out all of your applications and how you want them deployed. It looks like this:

.
+- apps
   +- app_0
      +- deployment.yml
      +- secrets.yml
   +- app_1
      +- deployment.yml
      +- secrets.yml
+- jobs

Gitops CLI Installation

Install the CLI tool from GitHub over SSH, which needs an SSH key registered with GitHub. Add --verbose to see what it is doing:
```
uv tool install git+ssh://git@github.com/uptick/gitops
```
Upgrade it with uv tool upgrade gitops.

Installing from PyPI (uv tool install gitops) still works, but we are moving away from it — use the git install.
Set up the environment variable GITOPS_APPS_DIRECTORY to invoke gitops from any directory.

Gitops Server Installation

Secrets should be placed in secrets.env. The example file secrets.example.env has the environment variables you will need to supply.

Ensure that the gitops service account has edit access to the namespace it is deploying to. An example RoleBinding is:

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: gitops-role-binding
  namespace: workforce
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: edit
subjects:
- kind: ServiceAccount
  name: default
  namespace: gitops

Contribution

We're using releaseplease, to publish a new version do the following:

Checkout a feature branch and make the changes
1. Make sure to follow instructions for writing commits by releaseplease
  1. fix: which represents bug fixes, and correlates to a SemVer patch.
  2. feat: which represents a new feature, and correlates to a SemVer minor.
  3. feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.
Push changes and get the PR approved
Once it is merged; an additional PR containing the release changes needs to be merged to create a release.

Release files for gitops 1.7.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gitops 1.7.1
File	Size	Uploaded
gitops-1.7.1.tar.gz	134.2 kB	Aug 17, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for gitops 1.7.1
File	Interpreter	ABI	Platform	Reset
gitops-1.7.1-py3-none-any.whl 26.0 kB Aug 17, 2026	Python 3	none	any	Details

Total release size: 160.2 kB

Release files / gitops-1.7.1.tar.gz

Download URL	gitops-1.7.1.tar.gz
Size	134.2 kB
Tags	Source
SHA-256 checksum How to use checksums	`9b61021e53c72c0911f90961a200a9e66b7151f2aae07d0458150c6d76532a3c`
BLAKE2b-256 checksum How to use checksums	`78cb90d8dc4f8996d9aa34b2278e9afb7f0954c5aef19748779874177823001a`
Upload date	Aug 17, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/uptick/gitops
Publishing commit: github.com/uptick/gitops/tree/a0ae7b6fdbe0e59bdceda1f52e5355c371776b27

Workflow

Publishing configuration: github.com/uptick/gitops/blob/a0ae7b6fdbe0e59bdceda1f52e5355c371776b27/.github/workflows/release-please.yaml
Publishing logs: github.com/uptick/gitops/actions/runs/31998930852/attempts/1

Artifact

Subject: gitops-1.7.1.tar.gz
SHA-256 checksum: 9b61021e53c72c0911f90961a200a9e66b7151f2aae07d0458150c6d76532a3c Verifying attestations

Release files / gitops-1.7.1-py3-none-any.whl

Download URL	gitops-1.7.1-py3-none-any.whl
Size	26.0 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`10de58e1f11c50789e364ee0cb44fd54da40f27c9d590139a3541594058afe6d`
BLAKE2b-256 checksum How to use checksums	`ab76082e89e466ecd7a932e4576bc6b9b92b7f89398bbea4454d38dafb142c9b`
Upload date	Aug 17, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/uptick/gitops
Publishing commit: github.com/uptick/gitops/tree/a0ae7b6fdbe0e59bdceda1f52e5355c371776b27

Workflow

Publishing configuration: github.com/uptick/gitops/blob/a0ae7b6fdbe0e59bdceda1f52e5355c371776b27/.github/workflows/release-please.yaml
Publishing logs: github.com/uptick/gitops/actions/runs/31998930852/attempts/1

Artifact

Subject: gitops-1.7.1-py3-none-any.whl
SHA-256 checksum: 10de58e1f11c50789e364ee0cb44fd54da40f27c9d590139a3541594058afe6d Verifying attestations