> ## Documentation Index
> Fetch the complete documentation index at: https://docs.akua.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Import a cluster
> Connect your existing Kubernetes infrastructure
If you already have a Kubernetes cluster from any source, you can import it into Akua. This works with any existing cluster — whether it's self-managed, from cloud providers (EKS, GKE, AKS), or other managed Kubernetes services. This lets you leverage your existing investment while gaining access to Akua's product install and marketplace features.
Consider [creating a managed cluster](/clusters/create) instead if you don't already have a Kubernetes cluster set up. Akua handles all the complex control plane management, so you can focus on your product rather than infrastructure operations. With imported clusters, control plane and worker operations are managed by your cloud provider or yourself, depending on your cluster type.
## When to import versus create
Choose to import your cluster if you already have Kubernetes infrastructure from EKS, GKE, AKS, or other providers, have invested in cluster setup, need specific configurations like custom networking or compliance requirements, or want to maintain your existing cluster management approach.
Consider creating a new managed cluster if you want Akua to handle the control plane with zero operational overhead, are new to Kubernetes and want to avoid complexity, prefer simplicity to focus on products rather than infrastructure, or need quick setup to get running in minutes.
## Prerequisites
Before importing your cluster, ensure it meets these requirements:
* **Kubernetes version**: 1.33+ (check with `kubectl version`)
* **Cluster access**: Admin permissions, network connectivity, valid kubeconfig
* **Required permissions**: Namespace management, workload deployment, RBAC operations
If you're not using admin kubeconfig, create a service account with these permissions and bind it to a ClusterRole:
```yaml RBAC configuration theme={null}
apiVersion: v1
kind: ServiceAccount
metadata:
name: akua-sa
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: akua-role
rules:
- apiGroups: ['']
resources: ['pods', 'pods/log', 'pods/exec', 'secrets']
verbs: ['get', 'list', 'watch', 'create', 'update', 'delete']
- apiGroups: ['apps']
resources: ['statefulsets', 'statefulsets/status']
verbs: ['get', 'list', 'watch', 'create', 'update', 'delete']
- apiGroups: ['']
resources: ['namespaces', 'namespaces/finalize']
verbs: ['get', 'list', 'watch', 'create', 'update', 'delete']
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: akua-role-binding
subjects:
- kind: ServiceAccount
name: akua-sa
roleRef:
kind: ClusterRole
name: akua-role
apiGroup: rbac.authorization.k8s.io
```
## How to import your cluster
Ensure you have a valid kubeconfig file with admin access to your cluster.
```bash Test cluster connection theme={null}
kubectl cluster-info
kubectl get nodes
```
```bash Export kubeconfig theme={null}
# If using default location
cat ~/.kube/config
# Or specify custom path
cat /path/to/your/kubeconfig
```
In the [clusters dashboard](https://akua.dev/clusters), click **"Import Cluster"** and choose **"Import Existing Cluster"**.
Click "Upload kubeconfig file" and select your kubeconfig file.
Copy your kubeconfig content and paste it into the text area.
Akua will automatically verify cluster accessibility, required permissions, Kubernetes version compatibility, and network connectivity.
If validation fails, check your kubeconfig and cluster permissions before retrying.
Set up how Akua will interact with your cluster: choose a cluster name, set the default namespace where new products will deploy, configure optional resource limits, and enable Akua observability (recommended). Then click **"Import Cluster"** to finalize the process.
Your cluster will appear in the dashboard as "Active" and ready for product installs.
## Limitations of imported clusters
Be aware of these differences compared to managed clusters:
Control plane and worker operations are managed by your cloud provider or yourself, depending on your cluster type. Akua does not manage the control plane for imported clusters.
You manage worker nodes yourself or through your cloud provider. Akua handles product installs but not worker infrastructure management.
You must handle Kubernetes version updates and cluster maintenance yourself. Akua does not automatically update imported clusters.
Limited monitoring compared to managed clusters. Akua provides application-layer monitoring, but infrastructure monitoring is your responsibility.
Not supported through Akua. You must configure and manage auto-scaling through your cloud provider or cluster management tools.
Application layer support only. Akua helps with product installs and troubleshooting, but full infrastructure support is not included.
## Troubleshooting
* Verify cluster is accessible from the internet
* Check that kubeconfig has admin permissions
* Ensure Kubernetes version is 1.33 or newer
* Test connection locally:
```bash Test connection theme={null}
kubectl cluster-info
```
```text Expected output theme={null}
Kubernetes control plane is running at https://xxx.xxx.xxx.xxx:6443
CoreDNS is running at https://xxx.xxx.xxx.xxx:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
```
* Verify cluster API server is publicly accessible
* Check firewall rules allow Akua IP ranges
* Ensure DNS resolution works for your cluster
* Test from external network:
```bash Test API server access theme={null}
curl -k https://your-cluster-api:6443
```
* Confirm kubeconfig has cluster-admin role
* Check RBAC is properly configured
* Verify service account has necessary permissions
* Test permissions:
```bash Test permissions theme={null}
kubectl auth can-i "*" "*" --all-namespaces
```
* Check cluster has adequate resources
* Verify default namespace exists and is accessible
* Review cluster events:
```bash Review events theme={null}
kubectl get events --sort-by=.metadata.creationTimestamp
```
* Contact support with deployment logs
## API
Manage clusters programmatically.
Endpoints, parameters, response shapes, and try-it playground.
Mint API tokens for programmatic access.
## Related topics
Set up a cluster where Akua manages the control plane.
Understand how clusters work in Akua.
Add persistent storage to your cluster.
Organize imported clusters with the rest of your infrastructure.