Skip to main content
Celum keeps no Git repositories and writes nothing to Git. Earlier releases registered GitLab repositories and committed cluster manifests and app files into them. That integration was removed in 1.202.0 (October 2026), after the ArgoCD integration it had served was removed in 1.56.0. This page stays so that links to it still say where things went.

​
Where things go now

“GitOps” still appears in Celum with one meaning: Flux reconciling the HelmReleases Celum applies on a supervisor.

​
If you used a repository

  • Revoke the GitLab tokens. Upgrading past 1.202.0 dropped the repositories and supervisor_repos tables and the tokens stored in them, but the tokens themselves are still valid in GitLab until you revoke them there.
  • Clusters created through GitLab keep running. Celum no longer edits or deletes their files in the repository; whatever reconciled from those files is now yours to manage, or to remove.
  • GITLAB_URL, GITLAB_TOKEN, GITLAB_PROJECT_ID and GITLAB_BRANCH are no longer read. Remove them from the backend’s environment.
The repository and GitLab routes went with it, and so did the repository:* and gitlab-app:* actions. A policy that still names those actions grants nothing.

GitOps & Apps overview

How an app reaches a supervisor or a tenant cluster today.

Create a cluster

The cluster form and the template wizard, both applying to the supervisor.

Cluster templates

Reusable cluster blueprints, rendered and applied without Git.

Day-2 operations

What is actually running on a cluster, read from its Helm state.