Skip to main content
Connect a Kubernetes cluster you already run to Qovery by installing the Qovery Operator. Qovery then installs and updates the Qovery stack on the cluster.
Install paths: EKS, GKE and Scaleway Kapsule use the Qovery Operator; AKS, k3s, on-premise and other clusters use qovery cluster install; with no cluster, qovery demo up runs a local k3s cluster

Pick the install path that matches your cluster. To let Qovery create and manage the cluster instead, see Create Your Cluster.

This page covers EKS, GKE and Scaleway Kapsule. For any other cluster, such as Azure AKS, k3s or an on-premise cluster, follow the installation with the Qovery CLI. See Which installation to use.No cluster yet? Run qovery demo up to try Qovery on a local k3s cluster with Docker. See Test & Learn Locally.
Want Qovery to provision and manage the cluster for you instead? See Create Your Cluster for the managed path (AWS, GCP, Azure, Scaleway).

​
Prerequisites

A Qovery organization, on any plan including Free
A running Kubernetes cluster on AWS (EKS), GCP (GKE) or Scaleway (Kapsule), with Kubernetes 1.31 or later and at least one node that can host a build, with 4 vCPU and 8 GiB of memory free, for example an 8 vCPU node. A 4 vCPU node is not enough.
kubectl access to the cluster with cluster-admin rights and helm, only to install the Operator once
A cloud credential for the provider of the cluster, with the required permissions
Active Qovery account - Sign up here
The Qovery Operator installation is in Preview. Run qovery cluster preflight with your kubeconfig pointing to the cluster, and check the full prerequisites before you start (default StorageClass when Loki uses a volume, EBS CSI driver on EKS, load balancer, no existing cert-manager, ExternalDNS or Envoy Gateway), because a missing one can make the deployment fail. See also the current limitations.

​
Installation

1

Create the cluster in the Console

Go to Clusters, add a cluster and, under Connect existing cluster (BYOK), select AWS, GCP or Scaleway. Fill in the cluster name, the credential and the region. On Configure Qovery Operator, keep the defaults and click Continue. Qovery adds the cluster to your organization.
2

Install the Qovery Operator

Download the Helm values file and run the Helm command shown in the Console, with a kubeconfig pointing to your cluster. The values file contains the cluster credential, so keep it private and delete it once the Operator is installed. Keep the page open, and the Console opens the cluster profile once the Operator connects.
3

Deploy the platform profile

Review the profile settings. Click Save and deploy if you changed one, or Deploy in the Manage deployment menu of the cluster to keep the defaults. Qovery installs the Qovery stack on the cluster.
See Bring Your Own Kubernetes (BYOK) for each step in detail, and its troubleshooting if the Operator does not connect or the deployment fails.

​
Next Steps

Deploy Your First App

Follow our quickstart guide

BYOK in detail

Prerequisites, permissions, limitations and troubleshooting

Get Help

Contact support

Kubernetes Changelog

Kubernetes cluster related updates