Skip to main content

Bring Your Cluster Setup

Atmosly allows you to import existing Kubernetes clusters from your cloud accounts into the platform for centralized management, monitoring, and add-on deployment.

Supported Cloud Providers​

ProviderCluster TypeDescription
AWS (EKS)Elastic Kubernetes ServiceImport existing EKS clusters with automatic node group discovery
GCP (GKE)Google Kubernetes EngineImport existing GKE clusters (Autopilot or Standard)

Import Workflow​

  1. Navigate to the Cluster module from the left menu.
  2. Click on Bring your cluster or Add Cluster in the top right corner.
  3. Select the Cloud Provider — AWS (EKS) or GCP (GKE).
  4. Select the Target Cloud Account where the cluster is running.
  5. Select the Region (AWS) or Zone (GCP) where the cluster is deployed.
  6. A list of available clusters will be displayed — select the cluster you want to import.
  7. Select the Cluster Type:
    • PUBLIC — Cluster with a publicly accessible API endpoint
    • PUBLIC + PRIVATE — Cluster with both public and private endpoints
    • PRIVATE — Cluster with a private-only API endpoint (requires ops-agent installation)
  8. Select the Access Mode — Read Only or Full Access (see below).
  9. Click Import to begin the import process.

Access Mode: Read Only vs Full Access​

When importing, you choose how much access Atmosly is granted over the cluster. This lets you evaluate the platform on a production cluster with minimal permissions before committing to write access.

Bring your cluster dialog with Read Only and Full Access mode selection
Access ModeWhat Atmosly Can DoWhen to Use
Read OnlyView nodes, pods, workloads, events, storage, and metrics. No agents are installed and no changes are made to the cluster.Safely evaluate Atmosly on production clusters with minimal permissions.
Full AccessEverything in Read Only, plus deployments, pipelines, add-on management, auto-remediation, and agents.Day-to-day management once you're ready to grant write access.

Upgrading from Read Only to Full Access​

You can move a read-only cluster to full access at any time — no re-import required:

  1. Open the cluster and choose Upgrade to Full Access (from the cluster actions).
  2. Atmosly checks whether the current credentials have the permissions needed for write operations.
  3. If additional permissions are required, Atmosly identifies the missing policies and shows you exactly what to grant.
  4. Apply the required permissions, then confirm the upgrade.
  5. Once upgraded, deployments, pipelines, auto-remediation, and agents become available.
note

A read-only import mints an on-demand, short-lived token for each operation and does not install agents. This is why some capabilities — deployments, add-on installs, and auto-remediation — only appear after upgrading to Full Access.

Private Cluster Import​

For PRIVATE clusters (where the API endpoint is not publicly accessible), Atmosly uses an ops-agent installed inside the cluster to communicate securely:

  1. After selecting a private cluster, Atmosly generates a one-time installation command.
  2. Run this command inside your cluster to install the ops-agent.
  3. The ops-agent establishes a secure connection back to Atmosly.
  4. Once connected, Atmosly can manage the cluster without direct API access.
note

The installation command includes a temporary security token that expires in 24 hours. Regenerate if installation is delayed.

Post-Import Capabilities​

Once imported, you can:

  • View node groups — Automatically discovered and listed from your cloud account
  • View nodes and pods — Monitor node health, pod status, and workloads
  • Deploy add-ons — Install add-ons directly from the Atmosly console
  • Run security scans — Evaluate cluster security with Kubescape
  • Manage RBAC — Configure role-based access control
  • View workloads — Monitor and manage Kubernetes deployments, statefulsets, jobs, etc.
note

Add-ons are not auto-installed on imported clusters. You can manually deploy required add-ons after import.

To edit the cluster and proceed with further configuration, refer to the Update & Upgrade Cluster section.

tip

For a lighter-weight import without cloud account integration, see Import Clusters via Token.