Akasha.
DocsAbout managed KubernetesGitOps with Flux

GitOps with Flux

Connect a Git or OCI source with Flux, bootstrap the current cluster state into a repository, and manage reconciliation.

The cluster's GitOps tab drives Flux, so your cluster continuously applies manifests from a Git repository or an OCI registry. The tab requires the Flux CD add-on (included in the CI & CD bundle).

Connect a source

  1. Open the cluster's GitOps tab and choose Connect Source.
  2. Pick a source type:
    • Git — enter the Repository URL, Branch (default main), and Path (default ./). For authentication, use PAT / Token (username defaults to git; leave the token blank for public repositories) or SSH Key (an unencrypted OpenSSH private key; the matching public key must be added to the repository as a deploy key).
    • OCI — enter an OCI URL such as oci://ghcr.io/org/manifests and a path.
  3. Create the source. Flux starts reconciling the manifests at the configured path.

An S3 / Bucket source type is also available: enter the S3 endpoint, bucket name, optional prefix, and access keys to reconcile manifests from an S3-compatible bucket.

The sources table shows each source's branch, last synced revision, and status. Failing sources display the error message with an Edit shortcut — you can fix the URL, branch, path, or credentials in place, and the source reconciles again automatically.

Bootstrap: export cluster state to Git

Bootstrap takes what is currently running in the cluster — deployments, services, config maps, RBAC, ingresses, and related resources — and pushes it as YAML manifests in a single commit to the connected Git repository. Bootstrap requires a Git source hosted on GitHub.

  1. Click Bootstrap on the Git source's row.
  2. Choose the target branch. Exporting to a separate branch lets you review the manifests in a pull request before merging.
  3. Confirm. The result reports how many files were committed.

After the manifests are merged into the watched branch, Flux manages those resources from Git: manual changes made with kubectl or the console are reverted on the next reconciliation.

Export: download cluster state

Export produces the same manifests as Bootstrap but downloads them as a zip archive instead of committing them — useful for reviewing offline or seeding a repository on another Git host.

Monitor and control reconciliation

  • Kustomizations — each source's Kustomizations are listed with their revision and readiness. You can edit the path inline, suspend and resume reconciliation, force an immediate reconcile, and expand a row to inspect conditions.
  • Helm Releases — Flux-managed Helm releases with chart, version, and status, plus suspend/resume and force-reconcile actions. Revision history, values, and rollback for releases installed through Akasha are available from the add-on configuration panel.
  • A summary bar shows counts of sources, Kustomizations, and Helm releases, and how many are ready.

Flux-managed resources are read-only in the console

Any resource that Flux manages is flagged "Managed by Flux" throughout the console, and its editors and scaling controls become read-only. This includes add-ons, virtual machines, and databases deployed through a Flux source. To change them, edit the manifests in the Git or OCI source and let Flux apply the change.