Install Qovery on Scaleway

​

Overview

• Automating Kapsule cluster creation and configuration
• Managing networking, load balancers, and DNS
• Providing built-in monitoring and logging
• Handling rolling updates and scaling
• Securing your infrastructure with best practices

​

Prerequisites

​

Step 1: Create Scaleway Credentials

​

Generate API Key

1

Access IAM Console

1. Log into Scaleway Console
2. Click your profile/organization name in the top-right
3. Select Identity and Access Management (IAM)

2

Create Application

1. Navigate to Applications tab
2. Click + Create application
3. Name it: qovery-manager or similar
4. Description: “Qovery cluster management”
5. Click Create application

Applications help organize API keys by purpose. You can reuse this application for multiple clusters.

3

Generate API Key

1. Click on your newly created application
2. Go to API keys tab
3. Click + Generate API key
4. Description: “Qovery cluster access”
5. Select Object Storage preferred Project (your main project)
6. Click Generate API key

Save these credentials immediately! The secret key is only shown once and cannot be retrieved later.

You’ll see:

• Access key ID: SCWxxxxxxxxxxxxxxxxx
• Secret access key: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Copy both to a secure location.

4

Configure Permissions

1. Go to Policies tab in IAM
2. Click + Create policy
3. Name it: qovery-permissions
4. Click Add rule for each of these permission sets:

Required Permissions:

• Containers - Full access (for Kapsule management)
• Network Services - Full access (for VPC, Load Balancers)
• Compute - Full access (for instances)
• Storage - Full access (for persistent volumes)
• VPC - Full access (for networking)
• IAM - Read only (IAMReadOnly, to check the permissions of the API key before deploying a cluster)

Optional Permissions:

• VPC Gateway - Full access (required if you want to use the Static IP for egress traffic feature)

5. Under Principal, attach this policy to your application
6. Click Create policy

These permissions allow Qovery to fully manage your Kubernetes infrastructure, including creating instances, configuring networking, and managing storage.

Why IAM read access? Before deploying a cluster, Qovery reads the policies attached to its API key to check that they grant the permission sets required by the features enabled on the cluster, for example VPC Gateway full access when Static IP for egress traffic is enabled. A missing permission is reported when the deployment starts, instead of failing midway through the infrastructure provisioning. IAMReadOnly gives list and read access to the users, groups, applications, policies, and API keys of your Organization. It does not allow Qovery to create, modify, or delete any of them.

IAMReadOnly is an Organization-level permission set, while the other permission sets apply to your project. Add it in a separate rule and select it under Organization management instead of Resource management.

5

Gather Required IDs

You’ll need these identifiers:Organization ID:

1. Go to Organization Settings
2. Copy the Organization ID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

Project ID:

1. Go to your Project Dashboard
2. Click Project settings
3. Copy the Project ID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

Keep these IDs handy - you’ll need them when configuring Qovery.

​

Add Credentials to Qovery

1

Start Cluster Creation

1. Go to Qovery Console
2. Go to your organization overview and click on the Clusters tab
3. Click Create Cluster
4. Select Scaleway as the cloud provider

2

Enter Credentials

Provide the information you gathered:

• Access Key ID: Your Scaleway access key
• Secret Access Key: Your Scaleway secret key
• Organization ID: Your Scaleway organization ID
• Project ID: Your Scaleway project ID

Click Next to validate the credentials.

3

Verify Connection

Qovery will test the credentials and verify it can access your Scaleway account.

If validation fails, double-check your API key has all required permissions attached via the policy.

​

Step 2: Configure Your Cluster

​

Basic Configuration

​

Node Pool Configuration

Node Pool Settings:
  - DEV1-M (2 vCPU, 3GB) - Development workloads
  - GP1-XS (4 vCPU, 16GB) - General purpose applications
  - COPARM1-4C-16G (4 vCPU ARM, 16GB) - Cost-optimized workloads

​

Step 3: Configure Network

​

Control Plane Options

​

Step 4: Deploy Your Cluster

​

What Gets Created

​

Post-Installation Steps

​

Troubleshooting

​

Advanced Configuration

​

Private Network Routes

1. Navigate to Private Networks in Scaleway Console
2. Attach your existing Private Network to the Kapsule cluster
3. Configure routes between networks
4. Update Security Groups to allow traffic
5. Test connectivity from pods

​

Using Existing Private Network

​

ARM Workloads

1. Use ARM-compatible container images (most official images support both)
2. Add node selector to deployments:
   nodeSelector:
     kubernetes.io/arch: arm64
   
3. Test ARM compatibility in staging before production
4. Mix ARM and x86 nodes using node selectors for different workloads

​

Multi-Availability Zone

1. Configure node pools across multiple AZs
2. Use pod anti-affinity to spread replicas
3. Configure topology spread constraints
4. Test failover scenarios
5. Monitor cross-AZ traffic costs

​

Best Practices

​

Next Steps

​

Additional Resources

• Scaleway Kapsule Documentation
• Scaleway Pricing Calculator
• Scaleway Status Page
• Qovery Status Page
• Qovery Kubernetes Changelog - Kubernetes cluster related updates