If you already have a Kubernetes cluster from any source, you can import it into CNAP. This works with any existing cluster - whether it’s self-managed, from cloud providers (EKS, GKE, AKS), or other managed Kubernetes services. This allows you to leverage your existing investment while gaining access to CNAP’s product deployment and marketplace features.

​
When to Import vs. Create

​
Import Your Cluster If You:

  • Have existing Kubernetes clusters - From EKS, GKE, AKS, or any other provider
  • Already invested in cluster setup - Self-managed or managed Kubernetes infrastructure
  • Need specific configurations - Custom networking, security policies, or compliance requirements
  • Want to keep existing cluster management - Maintain your current operational setup

​
Consider Creating a New Cluster If You:

  • Want CNAP-managed control plane - Zero operational overhead for Kubernetes management
  • Are new to Kubernetes - Avoid the complexity of cluster operations
  • Prefer simplicity - Focus on products, not infrastructure management
  • Need quick setup - Get running in minutes with minimal configuration
New to Kubernetes? Consider using CNAP’s managed clusters instead. We handle all the complex control plane management, so you can focus on your product rather than infrastructure operations.

​
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

​
How to Import Your Cluster

1

Prepare Your Kubeconfig

Ensure you have a valid kubeconfig file with admin access to your cluster.Test your connection:
kubectl cluster-info
kubectl get nodes
Export your kubeconfig:
# If using default location
cat ~/.kube/config

# Or specify custom path
cat /path/to/your/kubeconfig
2

Access Import Interface

  1. Navigate to the clusters section in your CNAP dashboard
  2. Click “Import Cluster”
  3. Choose “Import Existing Cluster”
3

Upload Kubeconfig

Option A: File Upload
  • Click “Upload kubeconfig file”
  • Select your kubeconfig file
  • CNAP will validate the configuration
Option B: Paste Content
  • Copy your kubeconfig content
  • Paste into the text area
  • Click “Validate Configuration”
4

Validate Connection

CNAP will test the connection and verify:
  • Cluster accessibility
  • Required permissions
  • Kubernetes version compatibility
  • Network connectivity
If validation fails, check your kubeconfig and cluster permissions before retrying.
5

Configure Import Settings

Set up how CNAP will interact with your cluster:
  • Cluster name - Descriptive name for your cluster
  • Default namespace - Where new products will deploy
  • Resource limits - Optional CPU/memory constraints
  • Monitoring - Enable CNAP observability (recommended)
6

Complete Import

Click “Import Cluster” to finalize the process.

​
Best Practices for Imported Clusters

​
Security Considerations

  • Use dedicated service accounts - Don’t use your personal admin credentials
  • Limit CNAP permissions - Create role-based access for CNAP operations
  • Network policies - Configure appropriate network segmentation
  • Regular updates - Keep your cluster and nodes updated

​
Resource Management

  • Reserve capacity - Ensure adequate resources for CNAP deployments
  • Monitor usage - Track resource consumption and scaling needs
  • Backup strategy - Maintain regular cluster and data backups
  • Disaster recovery - Have a plan for cluster failures

​
Maintenance and Updates

  • Coordinate updates - Plan Kubernetes version upgrades carefully
  • Test deployments - Validate CNAP functionality after changes
  • Monitor logs - Watch for issues with imported cluster operations
  • Communication - Notify CNAP support of major infrastructure changes

​
What Happens After Import?

Once your cluster is imported, you can:

Package Your Software

Turn your applications into sellable products

Monitor Cluster Health

Track resource usage and performance

Launch Your Marketplace

Create a storefront for your products

Learn Success Strategies

Discover how to build profitable cloud products

​
Limitations of Imported Clusters

Be aware of these limitations compared to managed clusters:
FeatureManaged ClustersImported Clusters
Control plane management✓ Fully managed✗ Your responsibility
Worker node provisioning✓ Automated options✗ Manual management
Automatic updates✓ Handled by CNAP✗ You must update
24/7 monitoring✓ Included~ Limited
Auto-scaling✓ Available✗ Not supported
Support level✓ Full infrastructure~ Application layer only

​
Troubleshooting

Considering a switch? If managing your own cluster becomes complex, you can always create a managed cluster and migrate your workloads. CNAP makes it easy to switch between infrastructure models.