Self-managed GitOps
Getting Started with Argo CD#
As described in the GitOps introduction , you can add your Cluster, ClusterStack, HetznerClusterStackReleaseTemplate, and HetznerBareMetalMachine manifests to your GitOps repository, and your GitOps operator will start managing them for you. If the manifests you add to the repository have the same names as those already in the Autopilot management cluster, the operator will start managing them without recreating the resources.
The same process can be applied to the deployment of Argo CD or Flux themselves. If you haven't set up Argo CD yet, follow the ArgoCD integration guide. For example, if you installed Argo CD via Helm, you can add this manifest to your GitOps repository:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: argocd
namespace: argocd
spec:
project: default
source:
chart: argo-cd
repoURL: https://argoproj.github.io/argo-helm
targetRevision: v7.0.0
helm:
releaseName: argocd
destination:
name: "in-cluster"
namespace: argocd
Now all your operations can be made from Git! Explore all of Syself's GitOps deployment features to learn more about what is possible.
Using Argo CD
Learn how to set up Argo CD for managing Kubernetes resources, which goes hand in hand with deploying applications - following all GitOps best practices.
Headless access to Syself Autopilot
How to access the Syself Autopilot management cluster without needing to interact with a browser, useful for pipelines and remote servers.