Skip to main content
Onboarding a Kubernetes cluster registers it with the Aviatrix Controller and enables Distributed Cloud Firewall to discover Kubernetes workloads (namespaces, services, pods, nodes, endpoint slices) and enforce policy on them via SmartGroups.

​
Before you start

Read Kubernetes Onboarding Prerequisites once. Each per-provider page below links back to the relevant anchors there rather than restating the requirements.

​
Private clusters

For clusters whose API server is not exposed to the public internet, set up private connectivity first via Onboarding Private Kubernetes Clusters , then return to the per-provider page. Pick the cluster type:

Onboard EKS Clusters

AWS-managed Kubernetes via the Aviatrix IAM principal or a service-account kubeconfig.

Onboard AKS Clusters

Azure-managed Kubernetes via the Aviatrix service principal or a service-account kubeconfig.

Onboard GKE Clusters

Google-managed Kubernetes via Terraform with the GCP service account or a service-account kubeconfig.

Onboard Self-Managed/Custom

kops, kubeadm, k3s, Rancher, and other clusters running in a supported cloud, using a service-account kubeconfig.