ankra-import-cluster

GitOps-backed cluster onboarding uses an ImportCluster manifest to connect a Git repository to your Kubernetes cluster. This manifest declares stacks of manifests and Helm addons, synchronizing them via a version-controlled repository to manage continuous deployment.

Yes, you can enforce deployment ordering by specifying parent relationships within your ImportCluster manifest. This dependency-aware mechanism ensures manifests and Helm addons deploy in the correct sequence to maintain reproducible environments.

Yes, importing clusters via an ImportCluster manifest applies to use cases such as importing EKS, GKE, AKS, or on-prem clusters. It connects these existing Kubernetes platforms to a version-controlled GitOps workflow to manage manifests and addons.

An ImportCluster manifest requires structured fields like spec.git_repository and stacks containing manifests and addons. Proper parent relationships must also be defined to enforce deployment order and promote reproducible environments.

You apply an ImportCluster manifest by running the command ankra cluster apply -f cluster.yaml --cluster <name>. This action wires the specified GitOps repository to your cluster and deploys the declared stacks.

The best way to manage manifests and Helm addons via Git is declaring them as stacks within an ImportCluster manifest. This method wires a GitOps repository to your cluster and uses dependency ordering to ensure proper deployment.