diff --git a/website/docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart.md b/website/docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart.md
index 5a8aeb5887..01c22385ec 100644
--- a/website/docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart.md
+++ b/website/docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2023-12-30"
+last_modified_on: "2024-11-21"
 title: "Quickstart"
 description: "Learn how to quickly install Qovery on your Amazon Web Services (AWS) account"
 ---
@@ -61,7 +61,7 @@ Then attach your credentials to your cluster and click on `Create`. Then, click
 
 ## Select your options
 
-Qovery propose multiple options that you can select to customize your installation. You can also change some of them later.
+Qovery propose multiple options that you can select to customize your installation. You can also change some of them later. Refer to this [guide][docs.using-qovery.configuration.clusters.aws] for more details on the available configurations.
 
 </li>
 
@@ -89,5 +89,6 @@ You should see your new cluster in the list of clusters.
 [docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.create-credentials]: /docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/create-credentials/
 [docs.getting-started.install-qovery.aws.cluster-managed-by-qovery]: /docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/
 [docs.using-qovery.configuration.clusters#creating-a-cluster]: /docs/using-qovery/configuration/clusters/#creating-a-cluster
+[docs.using-qovery.configuration.clusters.aws]: /docs/using-qovery/configuration/clusters/aws/
 [docs.using-qovery.configuration.organization]: /docs/using-qovery/configuration/organization/
 [guides.getting-started.deploy-your-first-application]: /guides/getting-started/deploy-your-first-application/
diff --git a/website/docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart.md.erb b/website/docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart.md.erb
index 50c4fd22bd..f6499ee51f 100644
--- a/website/docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart.md.erb
+++ b/website/docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart.md.erb
@@ -52,7 +52,7 @@ Then attach your credentials to your cluster and click on `Create`. Then, click
 
 ## Select your options
 
-Qovery propose multiple options that you can select to customize your installation. You can also change some of them later.
+Qovery propose multiple options that you can select to customize your installation. You can also change some of them later. Refer to this [guide][docs.using-qovery.configuration.clusters.aws] for more details on the available configurations.
 
 </li>
 
diff --git a/website/docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart.md b/website/docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart.md
index 8c80f72f04..a49b64d48f 100644
--- a/website/docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart.md
+++ b/website/docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2024-01-16"
+last_modified_on: "2024-11-21"
 title: "Quickstart"
 description: "Learn how to quickly install Qovery on your Google Cloud Platform (GCP) account"
 ---
@@ -68,6 +68,14 @@ Then attach your credentials to your cluster and click on `Create`. Then, click
 
 <li>
 
+## Select your options
+
+Qovery propose multiple options that you can select to customize your installation. You can also change some of them later. Refer to this [guide][docs.using-qovery.configuration.clusters.gcp] for more details on the available configurations.
+
+</li>
+
+<li>
+
 ## Install Qovery
 
 Click on `Create and Deploy` to create the cluster and install Qovery on it.
@@ -90,5 +98,6 @@ You should see your new cluster in the list of clusters.
 [docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.create-credentials]: /docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/create-credentials/
 [docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery]: /docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/
 [docs.using-qovery.configuration.clusters#creating-a-cluster]: /docs/using-qovery/configuration/clusters/#creating-a-cluster
+[docs.using-qovery.configuration.clusters.gcp]: /docs/using-qovery/configuration/clusters/gcp/
 [docs.using-qovery.configuration.organization]: /docs/using-qovery/configuration/organization/
 [guides.getting-started.deploy-your-first-application]: /guides/getting-started/deploy-your-first-application/
diff --git a/website/docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart.md.erb b/website/docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart.md.erb
index a0dc6a10de..05cc5d9a83 100644
--- a/website/docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart.md.erb
+++ b/website/docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart.md.erb
@@ -59,6 +59,14 @@ Then attach your credentials to your cluster and click on `Create`. Then, click
 
 <li>
 
+## Select your options
+
+Qovery propose multiple options that you can select to customize your installation. You can also change some of them later. Refer to this [guide][docs.using-qovery.configuration.clusters.gcp] for more details on the available configurations.
+
+</li>
+
+<li>
+
 ## Install Qovery
 
 Click on `Create and Deploy` to create the cluster and install Qovery on it.
diff --git a/website/docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart.md b/website/docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart.md
index 7f823586cd..e6c0859d48 100644
--- a/website/docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart.md
+++ b/website/docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2023-12-30"
+last_modified_on: "2024-11-21"
 title: "Quickstart"
 description: "Learn how to quickly install Qovery on your Scaleway (SCW) account"
 ---
@@ -45,6 +45,14 @@ Note that you can create multiple clusters on the same Scaleway account with dif
 
 <li>
 
+## Select your options
+
+Qovery propose multiple options that you can select to customize your installation. You can also change some of them later. Refer to this [guide][docs.using-qovery.configuration.clusters.scaleway] for more details on the available configurations.
+
+</li>
+
+<li>
+
 ## Attach Scaleway credentials
 
 Follow this [guide][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.create-credentials] to create your Scaleway credentials.
@@ -81,6 +89,7 @@ You should see your new cluster in the list of clusters.
 [docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.create-credentials]: /docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/create-credentials/
 [docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery]: /docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/
 [docs.using-qovery.configuration.clusters#creating-a-cluster]: /docs/using-qovery/configuration/clusters/#creating-a-cluster
+[docs.using-qovery.configuration.clusters.scaleway]: /docs/using-qovery/configuration/clusters/scaleway/
 [docs.using-qovery.configuration.organization]: /docs/using-qovery/configuration/organization/
 [guides.getting-started.deploy-your-first-application]: /guides/getting-started/deploy-your-first-application/
 [urls.scaleway]: https://www.scaleway.com
diff --git a/website/docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart.md.erb b/website/docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart.md.erb
index 929102c9b3..b51a3cead7 100644
--- a/website/docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart.md.erb
+++ b/website/docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart.md.erb
@@ -36,6 +36,14 @@ Note that you can create multiple clusters on the same Scaleway account with dif
 
 <li>
 
+## Select your options
+
+Qovery propose multiple options that you can select to customize your installation. You can also change some of them later. Refer to this [guide][docs.using-qovery.configuration.clusters.scaleway] for more details on the available configurations.
+
+</li>
+
+<li>
+
 ## Attach Scaleway credentials
 
 Follow this [guide][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.create-credentials] to create your Scaleway credentials.
diff --git a/website/docs/security-and-compliance.md b/website/docs/security-and-compliance.md
index 77cafa8b6d..a8611299d4 100644
--- a/website/docs/security-and-compliance.md
+++ b/website/docs/security-and-compliance.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2024-08-12"
+last_modified_on: "2024-11-26"
 title: Security and Compliance
 description: "Learn more about Security and Compliance in Qovery"
 sidebar_label: hidden
diff --git a/website/docs/useful-resources/faq.md b/website/docs/useful-resources/faq.md
index f1ffff3137..65f28661d9 100644
--- a/website/docs/useful-resources/faq.md
+++ b/website/docs/useful-resources/faq.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2024-09-24"
+last_modified_on: "2024-11-26"
 title: FAQ
 description: "Frequently Asked Questions"
 ---
@@ -48,7 +48,7 @@ Yes, absolutely!
 
 There isn't just one public cluster IP adress dedicated to external communication. However, [worker nodes][docs.using-qovery.configuration.clusters#what-is-a-cluster] inside your cluster each have a public IP automatically attached to them. You can view those default public IPs in the details of your worker nodes (EC2 instances for AWS users) which belong to the node group in your cluster.
 
-For improved security and control, the `Static IP` feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses. For more information on the `Static IP` feature and how to enable it at cluster creation, see [Static IP][docs.using-qovery.configuration.clusters#static-ip].
+For improved security and control, the `Static IP` feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses. For more information on the `Static IP` feature and how to enable it at cluster creation, see [Static IP on AWS][docs.using-qovery.configuration.clusters.aws#static-ip] or [Static IP on GCP][docs.using-qovery.configuration.clusters.gcp#static-ip].
 
 ## If I have N custom domains under the same root domain, do I need to create N CNAME records, or just creating one for the root domain is enough ?
 
@@ -115,8 +115,9 @@ Feel free to join our [forum][urls.qovery_forum] or contact us by email at hello
 [docs.using-qovery.configuration.application#auto-scaling]: /docs/using-qovery/configuration/application/#auto-scaling
 [docs.using-qovery.configuration.application]: /docs/using-qovery/configuration/application/
 [docs.using-qovery.configuration.clusters#how-does-qovery-handle-kubernetes-version-upgrades]: /docs/using-qovery/configuration/clusters/#how-does-qovery-handle-kubernetes-version-upgrades
-[docs.using-qovery.configuration.clusters#static-ip]: /docs/using-qovery/configuration/clusters/#static-ip
 [docs.using-qovery.configuration.clusters#what-is-a-cluster]: /docs/using-qovery/configuration/clusters/#what-is-a-cluster
+[docs.using-qovery.configuration.clusters.aws#static-ip]: /docs/using-qovery/configuration/clusters/aws/#static-ip
+[docs.using-qovery.configuration.clusters.gcp#static-ip]: /docs/using-qovery/configuration/clusters/gcp/#static-ip
 [docs.using-qovery.configuration.database]: /docs/using-qovery/configuration/database/
 [docs.using-qovery.configuration.environment]: /docs/using-qovery/configuration/environment/
 [docs.using-qovery.configuration.project]: /docs/using-qovery/configuration/project/
diff --git a/website/docs/useful-resources/faq.md.erb b/website/docs/useful-resources/faq.md.erb
index 8748a19c8a..2a1a6c0020 100644
--- a/website/docs/useful-resources/faq.md.erb
+++ b/website/docs/useful-resources/faq.md.erb
@@ -39,7 +39,7 @@ Yes, absolutely!
 
 There isn't just one public cluster IP adress dedicated to external communication. However, [worker nodes][docs.using-qovery.configuration.clusters#what-is-a-cluster] inside your cluster each have a public IP automatically attached to them. You can view those default public IPs in the details of your worker nodes (EC2 instances for AWS users) which belong to the node group in your cluster.
 
-For improved security and control, the `Static IP` feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses. For more information on the `Static IP` feature and how to enable it at cluster creation, see [Static IP][docs.using-qovery.configuration.clusters#static-ip].
+For improved security and control, the `Static IP` feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses. For more information on the `Static IP` feature and how to enable it at cluster creation, see [Static IP on AWS][docs.using-qovery.configuration.clusters.aws#static-ip] or [Static IP on GCP][docs.using-qovery.configuration.clusters.gcp#static-ip].
 
 ## If I have N custom domains under the same root domain, do I need to create N CNAME records, or just creating one for the root domain is enough ?
 
diff --git a/website/docs/using-qovery/configuration/clusters.md b/website/docs/using-qovery/configuration/clusters.md
index ff754065ff..c9d350eaf1 100644
--- a/website/docs/using-qovery/configuration/clusters.md
+++ b/website/docs/using-qovery/configuration/clusters.md
@@ -1,7 +1,8 @@
 ---
-last_modified_on: "2024-11-04"
+last_modified_on: "2024-11-27"
 title: "Clusters"
 description: "Learn how to configure your Kubernetes clusters on Qovery"
+sidebar_label: hidden
 ---
 
 import Steps from '@site/src/components/Steps';
@@ -16,7 +17,6 @@ If you are looking to install Qovery on your Kubernetes cluster, please refer to
 
 </Alert>
 
-
 <!--
      THIS FILE IS AUTOGENERATED!
 
@@ -27,16 +27,10 @@ If you are looking to install Qovery on your Kubernetes cluster, please refer to
 
 ## Managing your Clusters with Qovery
 
-From the [Qovery Console][urls.qovery_console], you can manage the settings of the clusters you want to run on your infrastructure. The clusters are then created (or updated) by the cloud provider that hosts them.
+From the [Qovery Console][urls.qovery_console], you can manage the clusters you want to run on your infrastructure.
 
 ### Creating a Cluster
 
-<Alert type="info">
-
-To install a cluster, Qovery needs a set of credentials to access your cloud provider account (example: AWS secret_access_key and access_key_id). If this is the first time you are installing a cluster with Qovery, have a look at this guide on how to get the credentials: [here for AWS][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials], [here for Scaleway][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials], [here for GCP][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials].
-
-</Alert>
-
 To create a cluster:
 
 <Steps headingDepth={3}>
@@ -48,332 +42,34 @@ Open your [Qovery Console][urls.qovery_console].
 </li>
 <li>
 
-On the left menu bar, click on the Cluster page:
+On the left menu bar, click on the Cluster page and click `Add Cluster`:
 
 <p align="center">
   <img src="/img/configuration/clusters/cluster_section_access.png" alt="Cluster Access" />
 </p>
 
-</li>
-<li>
-
-Click `Add Cluster`:
-
-<p align="center">
-  <img src="/img/configuration/clusters/add-cluster-button.png" alt="Add Cluster Button" />
-</p>
-
-</li>
-<li>
-
-In the `Create Cluster` window enter:
-
-* `Cluster name`: enter the name of your choice for your cluster.
-* `Description`: enter a description to identify better your cluster.
-* `Production cluster`: select this option if your cluster will be used for production.
-* `Cloud provider`: select your cloud provider.
-* `Region`: select the geographical area in which you want your cluster to be hosted.
-* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials], [Procedure for Scaleway account][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials], [Procedure for GCP account][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials]). Added credentials can be used later to create and manage additional cluster.
-
-To confirm, click `Next`.
-
-</li>
-<li>
-
-In the `Set Resources` window, select:
-
-* `Cluster`: select the cluster type to use. Please refer to this section for [more information][docs.using-qovery.configuration.clusters#why-do-i-need-a-cluster].
-* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..). Setting available only on AWS.
-* `Instance type`: select the type of [worker nodes][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster:
-* `Node auto-scaling`: define the minimum and the maximum number of worker nodes that your cluster can run. The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows. Please note that a minimum of 3 worker nodes is required to deploy your EKS cluster.
-
-<br/>
-
-<Alert type="warning">
-Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
-
-Please be aware that changing the instance type or disk size might cause a downtime for your service.
-
-For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
-
-Also, before downsizing, you need to ensure that your applications will still have enough resources to run correctly.
-
-</Alert>
-
-<br/>
-
-<Alert type="info">
-
-At the bottom of the window, you can see an estimate of the cost associated with the selected instance type.
-
-</Alert>
-
-For AWS EKS clusters, you have the possibility to enable `Karpenter` autoscaler to improve the efficiency and cost of running workloads on your cluster. You can check the [official documentation](https://karpenter.sh/docs/) for more information.
-
-<p align="center">
-  <img src="/img/configuration/clusters/karpenter.png" alt="Enable Karpenter" />
-</p>
-
-Today, only new non-production clusters are supported. It means you won't be able to enable it on your already existing cluster. It will be supported soon.
-
-By activating Karpenter, you have to set:
-* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..).
-* `Default node architecture`: If you build your application with the Qovery CI, your application will be built using this architecture by default.
-* `Spot instances`: In order to reduce even more your costs, you can also enable the spot instances on your clusters. Spot instances cost up to 90% less compared to On-Demand prices. But keep in mind that spot instances can be terminated by the cloud provider at any time. Check this [documentation](https://aws.amazon.com/ec2/spot/) for more information. Even if this flag is enabled, the statefulsets won't run on spot instances.
-
-<br/>
-
-<Alert type="warning">
-
-A SQS queue will be created. Before deploying your cluster, update the IAM permissions of the Qovery user, make sure to use the [latest version here](https://hub.qovery.com/files/qovery-iam-aws.json) to add the permission on SQS.
-
-</Alert>
-
-To confirm, click `Next`.
-
-</li>
-<li>
-
-*(Only for AWS K8S Clusters)* In the `Features` window, select the features you want to enable on your cluster.
-
-<Alert type="info">
-
-For more information, see [Features][docs.using-qovery.configuration.clusters#features].
-
-</Alert>
-
-</li>
-<li>
-
-In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
-
-You can now press the `Create and Install` button.
-
-Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
-
 </li>
 </ol>
-</Steps>
-
-
-### Managing your Cluster Settings
-
-To manage the settings of an existing cluster:
 
-<Steps headingDepth={3}>
-<ol>
-<li>
-
-Open your [Qovery Console][urls.qovery_console].
-
-</li>
-<li>
-
-On the left menu bar, click on the Cluster page:
+Refer to the specific installation guide for your cloud provider:
 
-<p align="center">
-  <img src="/img/configuration/clusters/cluster_section_access.png" alt="Cluster Access" />
-</p>
+<Jump to="/docs/using-qovery/configuration/clusters/aws-with-karpenter/">AWS with karpenter</Jump>
+<Jump to="/docs/using-qovery/configuration/clusters/aws/">AWS</Jump>
+<Jump to="/docs/using-qovery/configuration/clusters/gcp/">GCP</Jump>
+<Jump to="/docs/using-qovery/configuration/clusters/scaleway/">Scaleway</Jump>
 
-</li>
-<li>
-
-To access your cluster settings, click on the wheel button:
-
-<p align="center">
-  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
-</p>
-
-</li>
-
-</ol>
 </Steps>
 
-Below you can find a description of each section
-
-#### General
-
-The `General` tab allows you to define high-level information on your cluster:
-
-|Item|Description|
-|--------------|---------------------------|
-|Cluster Name|To edit the name of your cluster.|
-|Description|To enter or edit the description of your cluster.|
-|Production Cluster|To enter or edit the production flag of your cluster.|
-
-#### Credentials
-
-Here you can manage here the cloud provider credentials associated with your cluster.
-
-If you need to change the credentials:
-- generate a new set of credentials on your cloud provider([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials], [Procedure for Scaleway account][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials], [Procedure for GCP account][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials])
-- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
-
-In the dedicated fields, enter the credentials you created on your cloud provider account:
-
-| Account Provider | Field Labels                                   |
-|------------------|------------------------------------------------|
-| AWS              | `Access Key` and `Secret Access Key`           |
-| Scaleway         | `Scaleway Access Key`, `Scaleway Secret Key`, `Scaleway Project ID` and `Scaleway Organization ID`|
-| GCP              | `GCP JSON key`|
-
-Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
-
-#### Resources
-
-Qovery allows you to modify the resources allocated for your cluster:
-
-- In the `Instance type` dropdown menu, select the type of [worker node(s)][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster.
-- *(AWS users only)* In the `Node disk size (GB)` field, enter the disk capacity you want to allocate to your worker node(s) (meaning how much data, in gigabytes, you want each worker node to be able to hold).
-- *(EKS users only)* On the `Nodes auto-scaling`, define the range of worker nodes you want to deploy to your cluster.
-
-<Alert type="warning">
-Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
-
-For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
-
-</Alert>
-
-<br/>
-
-<Alert type="info">
-
-The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows.
-
-Please note that a minimum of 3 worker nodes is required to deploy your [EKS cluster][docs.using-qovery.configuration.clusters#creating-a-cluster].
-
-</Alert>
-
-#### Image registry
-
-In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
-This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
-
-The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
-
-Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
-
-#### Features
-
-The `Features` tab in your cluster settings allows you to check if the **Static IP**,  **Custom VPC subnet**, **Deploy on existing VPC** features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
-
-##### Static IP
-
-The **Static IP** feature is currently only available to clusters deployed on AWS and GCP with a VPC managed by Qovery and can only be enabled at cluster creation.
-
-By default, when your cluster is created, its worker nodes are allocated public IP addresses, which are used for external communication. For improved security and control, the **Static IP** feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses.
-
-Here is what will be deployed on `AWS`:
-* Nat Gateways
-* Elastic IPs
-* Private subnets
-
-Here is what will be deployed on `GCP`:
-* Cloud Nats
-* Static IPs
-* Routers
-
-Once set up, here is the procedure to find your static IP addresses on `AWS`:
-- On your AWS account, select the VPC service.
-- On the left menu, you’ll find Elastic IP addresses. Once on it, in the Allocated IPv4 address column, you’ll have your public IPs.
-
-Once set up, here is the procedure to find your static IP addresses on `GCP`:
-- On your GCP account, select the IP addresses service.
-- In the list you will find your static IP used by your cluster router.
-
-<Alert type="info">
-
-If you work in a sensitive business area such as financial technology, enabling the **Static IP** feature can help fulfil the security requirements of some of the external services you use, therefore making it easier for you to get whitelisted by them.
-
-This feature has been activated by default. Since February 1, 2024, AWS charge public IPv4 Addresses. Disabling it may cost you more, depending on the number of nodes in your cluster. Check this [link](https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/) for more information.
-
-</Alert>
-
-##### Custom VPC Subnet
-
-The **VPC** feature is currently only available to clusters deployed on AWS with a VPC managed by Qovery and can only be enabled at cluster creation.
-
-Virtual Private Cloud (VPC) peering allows you to set up a connection between your Qovery VPC and another VPC on your AWS account. This way, you can access resources stored on your AWS VPC directly from your Qovery applications.
-
-A VPC can only be used if it has at least one range of IP addresses called a **subnet**. When you create a cluster, Qovery automatically picks a default subnet for it. However, to perform VPC peering, you may want to define which specific VPC subnet you want to use, so that you can avoid any conflicting settings. To do so, you can enable the **Custom VPC Subnet** feature on your cluster. For more information on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
-
-##### Use existing VPC
-
-The **Deploy on existing VPC** feature is currently only available to clusters deployed on `AWS` and `GCP` when you select `Deploy on my existing VPC` VPC mode and can only be enabled at cluster creation.
-
-##### Use existing VPC - AWS:
-
-You have to specify the `VPC id` (1) and ensure that in your VPC settings you have enabled the `DNS hostnames` (2):
-
-<p align="center">
-  <img src="/img/configuration/clusters/existing_vpc_aws_dns_hostnames.png" alt="Existing VPC AWS DNS Hostnmaes" />
-</p>
-
-Then you have to specify the different subnets ids:
-
-**EKS**:
-
-The EKS subnets are mandatory, you have to specify at least **one subnet id per zone** (1) and ensure you have enabled the **auto-assign public IPv4 address** setting on your subnets (2).
-
-<p align="center">
-  <img src="/img/configuration/clusters/existing_vpc_aws_auto_assign.png" alt="Existing VPC AWS DNS Hostnmaes" />
-</p>
-
-<Alert type="info">
-
-If you have activated `Karpenter`, you will have to specify at least **one subnet id per zone**. These subnets have to be private and connected to internet through a NAT Gateway. They will be used for AWS Fargate profile.
-
-</Alert>
-
-**Managed databases**:
-
-This section is exclusively for enabling managed databases (container databases will be enabled by default).
-
-Depending on the managed databases you want to you use (**MongoDB**, **RDS:MySQL/PostgreSQL** and **Redis**), specify at least one subnet id per zone.
-
-##### Use existing VPC - GCP:
-
-In GCP you have two VPC modes: `Automatic` or `Custom`.
-
-If you are using an automatic or a custom VPC, you have to set:
-* Your VPC Name
-* External project id (optional): by default, the project id used is the one specified in the credentials file. But if your VPC is defined in another GCP project, you have to specify the Project id.
-
-In addition if you are using a custom VPC, you have to set:
-* Your Subnet range name (`https://console.cloud.google.com/networking/networks/details/<your-vpc>?project=<your-project>&pageTab=SUBNETS`)
-
-<Alert type="info">
-
-You can also specify (optional):
-  * Pod ipv4 address range name
-  * Additional cluster pod ipv4 ranges names (separated with a comma)
-  * Ipv4 service range name
-
-For these ranges, you have to create Secondary IPv4 ranges inside your subnet.
-
-</Alert>
-
-
-<Alert type="warning">
-
-Please keep in mind that enabling them later may not be possible.
-
-</Alert>
-
-#### Network
-
-The `Network` tab in your cluster settings allows you to update your Qovery VPC route table so that you can perform VPC peering. For step-by-step guidelines on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
-
 ### Performing Actions on your Clusters
 
 Qovery allows you to [update][docs.using-qovery.configuration.clusters#updating-a-cluster], [stop][docs.using-qovery.configuration.clusters#stopping-a-cluster], [restart][docs.using-qovery.configuration.clusters#restarting-a-cluster] or [delete][docs.using-qovery.configuration.clusters#deleting-a-cluster] your clusters at organization level.
 
-| Action                | Description    |
-|---------------------------------|---------|
-|[Updating a cluster][docs.using-qovery.configuration.clusters#updating-a-cluster]| To redeploy your cluster after a change has been made to it.|
-|[Stopping a cluster][docs.using-qovery.configuration.clusters#stopping-a-cluster]| To temporarily stop your cluster. Some services you have subscribed to via your cloud provider may still be active and incur costs when your cluster is stopped. For more information, see [Stopping a cluster][docs.using-qovery.configuration.clusters#stopping-a-cluster].|
-|[Restarting a cluster][docs.using-qovery.configuration.clusters#restarting-a-cluster]| To restart your cluster after it has been temporarily stopped.|
-|[Deleting a cluster][docs.using-qovery.configuration.clusters#deleting-a-cluster]| To delete your cluster. This is final and needs to be done properly to ensure all the services deployed by Qovery on your cloud provider's account are disabled, with no leftover cloud-related costs. For more information, see [Deleting a cluster][docs.using-qovery.configuration.clusters#deleting-a-cluster].|
+| Action                | Description    | Cloud provider    |
+|---------------------------------|---------|---------|
+|[Updating a cluster][docs.using-qovery.configuration.clusters#updating-a-cluster]| To redeploy your cluster after a change has been made to it.| ![AWS Icon](/img/advanced_settings/aws.svg) ![GCP Icon](/img/advanced_settings/gcp.svg) ![SCW Icon](/img/advanced_settings/scaleway.svg) |
+|[Stopping a cluster][docs.using-qovery.configuration.clusters#stopping-a-cluster]| To temporarily stop your cluster. Some services you have subscribed to via your cloud provider may still be active and incur costs when your cluster is stopped. For more information, see [Stopping a cluster][docs.using-qovery.configuration.clusters#stopping-a-cluster].| ![AWS Icon](/img/advanced_settings/aws.svg) |
+|[Restarting a cluster][docs.using-qovery.configuration.clusters#restarting-a-cluster]| To restart your cluster after it has been temporarily stopped.| ![AWS Icon](/img/advanced_settings/aws.svg) ![GCP Icon](/img/advanced_settings/gcp.svg) ![SCW Icon](/img/advanced_settings/scaleway.svg) |
+|[Deleting a cluster][docs.using-qovery.configuration.clusters#deleting-a-cluster]| To delete your cluster. This is final and needs to be done properly to ensure all the services deployed by Qovery on your cloud provider's account are disabled, with no leftover cloud-related costs. For more information, see [Deleting a cluster][docs.using-qovery.configuration.clusters#deleting-a-cluster].| ![AWS Icon](/img/advanced_settings/aws.svg) ![GCP Icon](/img/advanced_settings/gcp.svg) ![SCW Icon](/img/advanced_settings/scaleway.svg) |
 
 To access these actions:
 
@@ -386,11 +82,7 @@ Open your [Qovery Console][urls.qovery_console].
 </li>
 <li>
 
-On the left menu bar, click on the Cluster page:
-
-<p align="center">
-  <img src="/img/configuration/clusters/cluster_section_access.png" alt="Cluster Access" />
-</p>
+On the left menu bar, click on the Cluster page.
 
 </li>
 <li>
@@ -572,13 +264,6 @@ The error message should provide you enough information to solve the issue. If t
 
 </Alert>
 
- You can add the generated public SSH key at cluster creation (see [Creating a Cluster][docs.using-qovery.configuration.clusters#creating-a-cluster]), or later from your cluster settings.
-
- To do so:
-  - on your [Qovery Console][urls.qovery_console], access your [cluster settings][docs.using-qovery.configuration.clusters#managing-your-cluster-settings].
-  - In the `Remote Access` tab, enter your SSH key and click `Save`.
-  - Launch the [Update Cluster][docs.using-qovery.configuration.clusters] action to propagate the new key.
-
 ## Use custom domain and wildcard TLS for the whole cluster (beta)
 
 By default, Qovery provides a domain (ex `bool.sh`) on every deployed cluster. It is used to provide a DNS and TLS certificate to every application requiring external access on a cluster.
@@ -625,7 +310,6 @@ To clean up a Qovery cluster from your cloud provider account, go to `AWS Consol
 | 3    | Click `Add`.                                                                                                                                 |
 | 4    | Click `Preview Resources`. <br /> All your Qovery clusters are now displayed in the `Group resources` table, and you can delete them by hand.|
 
-
 ## FAQ
 
 ### What is a cluster?
@@ -696,21 +380,10 @@ Security is our main concern. When a vulnerability is found, here are the action
 
 
 [docs.getting-started.basic-concepts#cluster]: /docs/getting-started/basic-concepts/#cluster
-[docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials]: /docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart/#attach-aws-credentials
-[docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials]: /docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart/#attach-gcp-credentials
 [docs.getting-started.install-qovery.kubernetes]: /docs/getting-started/install-qovery/kubernetes/
-[docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials]: /docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart/#attach-scaleway-credentials
-[docs.using-qovery.configuration.clusters#creating-a-cluster]: /docs/using-qovery/configuration/clusters/#creating-a-cluster
 [docs.using-qovery.configuration.clusters#deleting-a-cluster]: /docs/using-qovery/configuration/clusters/#deleting-a-cluster
-[docs.using-qovery.configuration.clusters#features]: /docs/using-qovery/configuration/clusters/#features
 [docs.using-qovery.configuration.clusters#logs]: /docs/using-qovery/configuration/clusters/#logs
-[docs.using-qovery.configuration.clusters#managing-your-cluster-settings]: /docs/using-qovery/configuration/clusters/#managing-your-cluster-settings
 [docs.using-qovery.configuration.clusters#restarting-a-cluster]: /docs/using-qovery/configuration/clusters/#restarting-a-cluster
 [docs.using-qovery.configuration.clusters#stopping-a-cluster]: /docs/using-qovery/configuration/clusters/#stopping-a-cluster
 [docs.using-qovery.configuration.clusters#updating-a-cluster]: /docs/using-qovery/configuration/clusters/#updating-a-cluster
-[docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]: /docs/using-qovery/configuration/clusters/#what-are-the-different-instance-types-available-when-creating-a-cluster
-[docs.using-qovery.configuration.clusters#what-is-a-cluster]: /docs/using-qovery/configuration/clusters/#what-is-a-cluster
-[docs.using-qovery.configuration.clusters#why-do-i-need-a-cluster]: /docs/using-qovery/configuration/clusters/#why-do-i-need-a-cluster
-[docs.using-qovery.configuration.clusters]: /docs/using-qovery/configuration/clusters/
-[docs.using-qovery.deployment.image-mirroring]: /docs/using-qovery/deployment/image-mirroring/
 [urls.qovery_console]: https://console.qovery.com
diff --git a/website/docs/using-qovery/configuration/clusters.md.erb b/website/docs/using-qovery/configuration/clusters.md.erb
index 6cad1f5b09..533050e204 100644
--- a/website/docs/using-qovery/configuration/clusters.md.erb
+++ b/website/docs/using-qovery/configuration/clusters.md.erb
@@ -2,6 +2,7 @@
 last_modified_on: "2022-05-19"
 title: "Clusters"
 description: "Learn how to configure your Kubernetes clusters on Qovery"
+sidebar_label: hidden
 ---
 
 import Steps from '@site/src/components/Steps';
@@ -16,19 +17,12 @@ If you are looking to install Qovery on your Kubernetes cluster, please refer to
 
 </Alert>
 
-
 ## Managing your Clusters with Qovery
 
-From the [Qovery Console][urls.qovery_console], you can manage the settings of the clusters you want to run on your infrastructure. The clusters are then created (or updated) by the cloud provider that hosts them.
+From the [Qovery Console][urls.qovery_console], you can manage the clusters you want to run on your infrastructure.
 
 ### Creating a Cluster
 
-<Alert type="info">
-
-To install a cluster, Qovery needs a set of credentials to access your cloud provider account (example: AWS secret_access_key and access_key_id). If this is the first time you are installing a cluster with Qovery, have a look at this guide on how to get the credentials: [here for AWS][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials], [here for Scaleway][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials], [here for GCP][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials].
-
-</Alert>
-
 To create a cluster:
 
 <Steps headingDepth={3}>
@@ -40,332 +34,31 @@ Open your [Qovery Console][urls.qovery_console].
 </li>
 <li>
 
-On the left menu bar, click on the Cluster page:
+On the left menu bar, click on the Cluster page and click `Add Cluster`:
 
 <p align="center">
   <img src="/img/configuration/clusters/cluster_section_access.png" alt="Cluster Access" />
 </p>
 
-</li>
-<li>
-
-Click `Add Cluster`:
-
-<p align="center">
-  <img src="/img/configuration/clusters/add-cluster-button.png" alt="Add Cluster Button" />
-</p>
-
-</li>
-<li>
-
-In the `Create Cluster` window enter:
-
-* `Cluster name`: enter the name of your choice for your cluster.
-* `Description`: enter a description to identify better your cluster.
-* `Production cluster`: select this option if your cluster will be used for production.
-* `Cloud provider`: select your cloud provider.
-* `Region`: select the geographical area in which you want your cluster to be hosted.
-* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials], [Procedure for Scaleway account][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials], [Procedure for GCP account][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials]). Added credentials can be used later to create and manage additional cluster.
-
-To confirm, click `Next`.
-
-</li>
-<li>
-
-In the `Set Resources` window, select:
-
-* `Cluster`: select the cluster type to use. Please refer to this section for [more information][docs.using-qovery.configuration.clusters#why-do-i-need-a-cluster].
-* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..). Setting available only on AWS.
-* `Instance type`: select the type of [worker nodes][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster:
-* `Node auto-scaling`: define the minimum and the maximum number of worker nodes that your cluster can run. The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows. Please note that a minimum of 3 worker nodes is required to deploy your EKS cluster.
-
-<br/>
-
-<Alert type="warning">
-Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
-
-Please be aware that changing the instance type or disk size might cause a downtime for your service.
-
-For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
-
-Also, before downsizing, you need to ensure that your applications will still have enough resources to run correctly.
-
-</Alert>
-
-<br/>
-
-<Alert type="info">
-
-At the bottom of the window, you can see an estimate of the cost associated with the selected instance type.
-
-</Alert>
-
-For AWS EKS clusters, you have the possibility to enable `Karpenter` autoscaler to improve the efficiency and cost of running workloads on your cluster. You can check the [official documentation](https://karpenter.sh/docs/) for more information.
-
-<p align="center">
-  <img src="/img/configuration/clusters/karpenter.png" alt="Enable Karpenter" />
-</p>
-
-Today, only new non-production clusters are supported. It means you won't be able to enable it on your already existing cluster. It will be supported soon.
-
-By activating Karpenter, you have to set:
-* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..).
-* `Default node architecture`: If you build your application with the Qovery CI, your application will be built using this architecture by default.
-* `Spot instances`: In order to reduce even more your costs, you can also enable the spot instances on your clusters. Spot instances cost up to 90% less compared to On-Demand prices. But keep in mind that spot instances can be terminated by the cloud provider at any time. Check this [documentation](https://aws.amazon.com/ec2/spot/) for more information. Even if this flag is enabled, the statefulsets won't run on spot instances.
-
-<br/>
-
-<Alert type="warning">
-
-A SQS queue will be created. Before deploying your cluster, update the IAM permissions of the Qovery user, make sure to use the [latest version here](https://hub.qovery.com/files/qovery-iam-aws.json) to add the permission on SQS.
-
-</Alert>
-
-To confirm, click `Next`.
-
-</li>
-<li>
-
-*(Only for AWS K8S Clusters)* In the `Features` window, select the features you want to enable on your cluster.
-
-<Alert type="info">
-
-For more information, see [Features][docs.using-qovery.configuration.clusters#features].
-
-</Alert>
-
-</li>
-<li>
-
-In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
-
-You can now press the `Create and Install` button.
-
-Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
-
 </li>
 </ol>
-</Steps>
-
-
-### Managing your Cluster Settings
-
-To manage the settings of an existing cluster:
 
-<Steps headingDepth={3}>
-<ol>
-<li>
-
-Open your [Qovery Console][urls.qovery_console].
-
-</li>
-<li>
-
-On the left menu bar, click on the Cluster page:
+Refer to the specific installation guide for your cloud provider:
 
-<p align="center">
-  <img src="/img/configuration/clusters/cluster_section_access.png" alt="Cluster Access" />
-</p>
+<%= subpages() %>
 
-</li>
-<li>
-
-To access your cluster settings, click on the wheel button:
-
-<p align="center">
-  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
-</p>
-
-</li>
-
-</ol>
 </Steps>
 
-Below you can find a description of each section
-
-#### General
-
-The `General` tab allows you to define high-level information on your cluster:
-
-|Item|Description|
-|--------------|---------------------------|
-|Cluster Name|To edit the name of your cluster.|
-|Description|To enter or edit the description of your cluster.|
-|Production Cluster|To enter or edit the production flag of your cluster.|
-
-#### Credentials
-
-Here you can manage here the cloud provider credentials associated with your cluster.
-
-If you need to change the credentials:
-- generate a new set of credentials on your cloud provider([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials], [Procedure for Scaleway account][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials], [Procedure for GCP account][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials])
-- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
-
-In the dedicated fields, enter the credentials you created on your cloud provider account:
-
-| Account Provider | Field Labels                                   |
-|------------------|------------------------------------------------|
-| AWS              | `Access Key` and `Secret Access Key`           |
-| Scaleway         | `Scaleway Access Key`, `Scaleway Secret Key`, `Scaleway Project ID` and `Scaleway Organization ID`|
-| GCP              | `GCP JSON key`|
-
-Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
-
-#### Resources
-
-Qovery allows you to modify the resources allocated for your cluster:
-
-- In the `Instance type` dropdown menu, select the type of [worker node(s)][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster.
-- *(AWS users only)* In the `Node disk size (GB)` field, enter the disk capacity you want to allocate to your worker node(s) (meaning how much data, in gigabytes, you want each worker node to be able to hold).
-- *(EKS users only)* On the `Nodes auto-scaling`, define the range of worker nodes you want to deploy to your cluster.
-
-<Alert type="warning">
-Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
-
-For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
-
-</Alert>
-
-<br/>
-
-<Alert type="info">
-
-The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows.
-
-Please note that a minimum of 3 worker nodes is required to deploy your [EKS cluster][docs.using-qovery.configuration.clusters#creating-a-cluster].
-
-</Alert>
-
-#### Image registry
-
-In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
-This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
-
-The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
-
-Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
-
-#### Features
-
-The `Features` tab in your cluster settings allows you to check if the **Static IP**,  **Custom VPC subnet**, **Deploy on existing VPC** features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
-
-##### Static IP
-
-The **Static IP** feature is currently only available to clusters deployed on AWS and GCP with a VPC managed by Qovery and can only be enabled at cluster creation.
-
-By default, when your cluster is created, its worker nodes are allocated public IP addresses, which are used for external communication. For improved security and control, the **Static IP** feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses.
-
-Here is what will be deployed on `AWS`:
-* Nat Gateways
-* Elastic IPs
-* Private subnets
-
-Here is what will be deployed on `GCP`:
-* Cloud Nats
-* Static IPs
-* Routers
-
-Once set up, here is the procedure to find your static IP addresses on `AWS`:
-- On your AWS account, select the VPC service.
-- On the left menu, you’ll find Elastic IP addresses. Once on it, in the Allocated IPv4 address column, you’ll have your public IPs.
-
-Once set up, here is the procedure to find your static IP addresses on `GCP`:
-- On your GCP account, select the IP addresses service.
-- In the list you will find your static IP used by your cluster router.
-
-<Alert type="info">
-
-If you work in a sensitive business area such as financial technology, enabling the **Static IP** feature can help fulfil the security requirements of some of the external services you use, therefore making it easier for you to get whitelisted by them.
-
-This feature has been activated by default. Since February 1, 2024, AWS charge public IPv4 Addresses. Disabling it may cost you more, depending on the number of nodes in your cluster. Check this [link](https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/) for more information.
-
-</Alert>
-
-##### Custom VPC Subnet
-
-The **VPC** feature is currently only available to clusters deployed on AWS with a VPC managed by Qovery and can only be enabled at cluster creation.
-
-Virtual Private Cloud (VPC) peering allows you to set up a connection between your Qovery VPC and another VPC on your AWS account. This way, you can access resources stored on your AWS VPC directly from your Qovery applications.
-
-A VPC can only be used if it has at least one range of IP addresses called a **subnet**. When you create a cluster, Qovery automatically picks a default subnet for it. However, to perform VPC peering, you may want to define which specific VPC subnet you want to use, so that you can avoid any conflicting settings. To do so, you can enable the **Custom VPC Subnet** feature on your cluster. For more information on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
-
-##### Use existing VPC
-
-The **Deploy on existing VPC** feature is currently only available to clusters deployed on `AWS` and `GCP` when you select `Deploy on my existing VPC` VPC mode and can only be enabled at cluster creation.
-
-##### Use existing VPC - AWS:
-
-You have to specify the `VPC id` (1) and ensure that in your VPC settings you have enabled the `DNS hostnames` (2):
-
-<p align="center">
-  <img src="/img/configuration/clusters/existing_vpc_aws_dns_hostnames.png" alt="Existing VPC AWS DNS Hostnmaes" />
-</p>
-
-Then you have to specify the different subnets ids:
-
-**EKS**:
-
-The EKS subnets are mandatory, you have to specify at least **one subnet id per zone** (1) and ensure you have enabled the **auto-assign public IPv4 address** setting on your subnets (2).
-
-<p align="center">
-  <img src="/img/configuration/clusters/existing_vpc_aws_auto_assign.png" alt="Existing VPC AWS DNS Hostnmaes" />
-</p>
-
-<Alert type="info">
-
-If you have activated `Karpenter`, you will have to specify at least **one subnet id per zone**. These subnets have to be private and connected to internet through a NAT Gateway. They will be used for AWS Fargate profile.
-
-</Alert>
-
-**Managed databases**:
-
-This section is exclusively for enabling managed databases (container databases will be enabled by default).
-
-Depending on the managed databases you want to you use (**MongoDB**, **RDS:MySQL/PostgreSQL** and **Redis**), specify at least one subnet id per zone.
-
-##### Use existing VPC - GCP:
-
-In GCP you have two VPC modes: `Automatic` or `Custom`.
-
-If you are using an automatic or a custom VPC, you have to set:
-* Your VPC Name
-* External project id (optional): by default, the project id used is the one specified in the credentials file. But if your VPC is defined in another GCP project, you have to specify the Project id.
-
-In addition if you are using a custom VPC, you have to set:
-* Your Subnet range name (`https://console.cloud.google.com/networking/networks/details/<your-vpc>?project=<your-project>&pageTab=SUBNETS`)
-
-<Alert type="info">
-
-You can also specify (optional):
-  * Pod ipv4 address range name
-  * Additional cluster pod ipv4 ranges names (separated with a comma)
-  * Ipv4 service range name
-
-For these ranges, you have to create Secondary IPv4 ranges inside your subnet.
-
-</Alert>
-
-
-<Alert type="warning">
-
-Please keep in mind that enabling them later may not be possible.
-
-</Alert>
-
-#### Network
-
-The `Network` tab in your cluster settings allows you to update your Qovery VPC route table so that you can perform VPC peering. For step-by-step guidelines on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
-
 ### Performing Actions on your Clusters
 
 Qovery allows you to [update][docs.using-qovery.configuration.clusters#updating-a-cluster], [stop][docs.using-qovery.configuration.clusters#stopping-a-cluster], [restart][docs.using-qovery.configuration.clusters#restarting-a-cluster] or [delete][docs.using-qovery.configuration.clusters#deleting-a-cluster] your clusters at organization level.
 
-| Action                | Description    |
-|---------------------------------|---------|
-|[Updating a cluster][docs.using-qovery.configuration.clusters#updating-a-cluster]| To redeploy your cluster after a change has been made to it.|
-|[Stopping a cluster][docs.using-qovery.configuration.clusters#stopping-a-cluster]| To temporarily stop your cluster. Some services you have subscribed to via your cloud provider may still be active and incur costs when your cluster is stopped. For more information, see [Stopping a cluster][docs.using-qovery.configuration.clusters#stopping-a-cluster].|
-|[Restarting a cluster][docs.using-qovery.configuration.clusters#restarting-a-cluster]| To restart your cluster after it has been temporarily stopped.|
-|[Deleting a cluster][docs.using-qovery.configuration.clusters#deleting-a-cluster]| To delete your cluster. This is final and needs to be done properly to ensure all the services deployed by Qovery on your cloud provider's account are disabled, with no leftover cloud-related costs. For more information, see [Deleting a cluster][docs.using-qovery.configuration.clusters#deleting-a-cluster].|
+| Action                | Description    | Cloud provider    |
+|---------------------------------|---------|---------|
+|[Updating a cluster][docs.using-qovery.configuration.clusters#updating-a-cluster]| To redeploy your cluster after a change has been made to it.| ![AWS Icon](/img/advanced_settings/aws.svg) ![GCP Icon](/img/advanced_settings/gcp.svg) ![SCW Icon](/img/advanced_settings/scaleway.svg) |
+|[Stopping a cluster][docs.using-qovery.configuration.clusters#stopping-a-cluster]| To temporarily stop your cluster. Some services you have subscribed to via your cloud provider may still be active and incur costs when your cluster is stopped. For more information, see [Stopping a cluster][docs.using-qovery.configuration.clusters#stopping-a-cluster].| ![AWS Icon](/img/advanced_settings/aws.svg) |
+|[Restarting a cluster][docs.using-qovery.configuration.clusters#restarting-a-cluster]| To restart your cluster after it has been temporarily stopped.| ![AWS Icon](/img/advanced_settings/aws.svg) ![GCP Icon](/img/advanced_settings/gcp.svg) ![SCW Icon](/img/advanced_settings/scaleway.svg) |
+|[Deleting a cluster][docs.using-qovery.configuration.clusters#deleting-a-cluster]| To delete your cluster. This is final and needs to be done properly to ensure all the services deployed by Qovery on your cloud provider's account are disabled, with no leftover cloud-related costs. For more information, see [Deleting a cluster][docs.using-qovery.configuration.clusters#deleting-a-cluster].| ![AWS Icon](/img/advanced_settings/aws.svg) ![GCP Icon](/img/advanced_settings/gcp.svg) ![SCW Icon](/img/advanced_settings/scaleway.svg) |
 
 To access these actions:
 
@@ -378,11 +71,7 @@ Open your [Qovery Console][urls.qovery_console].
 </li>
 <li>
 
-On the left menu bar, click on the Cluster page:
-
-<p align="center">
-  <img src="/img/configuration/clusters/cluster_section_access.png" alt="Cluster Access" />
-</p>
+On the left menu bar, click on the Cluster page.
 
 </li>
 <li>
@@ -564,13 +253,6 @@ The error message should provide you enough information to solve the issue. If t
 
 </Alert>
 
- You can add the generated public SSH key at cluster creation (see [Creating a Cluster][docs.using-qovery.configuration.clusters#creating-a-cluster]), or later from your cluster settings.
-
- To do so:
-  - on your [Qovery Console][urls.qovery_console], access your [cluster settings][docs.using-qovery.configuration.clusters#managing-your-cluster-settings].
-  - In the `Remote Access` tab, enter your SSH key and click `Save`.
-  - Launch the [Update Cluster][docs.using-qovery.configuration.clusters] action to propagate the new key.
-
 ## Use custom domain and wildcard TLS for the whole cluster (beta)
 
 By default, Qovery provides a domain (ex `bool.sh`) on every deployed cluster. It is used to provide a DNS and TLS certificate to every application requiring external access on a cluster.
@@ -617,7 +299,6 @@ To clean up a Qovery cluster from your cloud provider account, go to `AWS Consol
 | 3    | Click `Add`.                                                                                                                                 |
 | 4    | Click `Preview Resources`. <br /> All your Qovery clusters are now displayed in the `Group resources` table, and you can delete them by hand.|
 
-
 ## FAQ
 
 ### What is a cluster?
diff --git a/website/docs/using-qovery/configuration/clusters/aws-with-karpenter.md b/website/docs/using-qovery/configuration/clusters/aws-with-karpenter.md
new file mode 100644
index 0000000000..3a92f0f07b
--- /dev/null
+++ b/website/docs/using-qovery/configuration/clusters/aws-with-karpenter.md
@@ -0,0 +1,318 @@
+---
+last_modified_on: "2024-11-27"
+title: "AWS EKS with Karpenter"
+description: "Learn how to configure your AWS Kubernetes clusters with Karpenter on Qovery"
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+import Steps from '@site/src/components/Steps';
+
+import Jump from '@site/src/components/Jump';
+import Alert from '@site/src/components/Alert';
+import Assumptions from '@site/src/components/Assumptions';
+
+<Alert type="warning">
+
+Karpenter is only available for non-production clusters. If you have created a production cluster, this option will not be visible.
+
+</Alert>
+
+Karpenter automatically launches just the right compute resources to handle your cluster's applications. It is designed to let you take full advantage of the cloud with fast and simple compute provisioning for Kubernetes clusters.
+You can our [blog post](https://www.qovery.com/blog/save-up-to-60-on-aws-costs-with-eks-and-karpenter/) for more information."
+
+### Creating a AWS EKS Cluster with Karpenter
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Click on `AWS` as hosting mode and then `Qovery Managed` option:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_hosting_selection_aws.png" alt="Cluster AWS" />
+</p>
+
+In the `Create Cluster` window enter:
+
+* `Cluster name`: enter the name of your choice for your cluster.
+* `Description`: enter a description to identify better your cluster.
+* `Production cluster`: select this option if your cluster will be used for production. Note: Karpenter is currently only available for non-production clusters.
+* `Region`: select the geographical area in which you want your cluster to be hosted.
+* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials]). Added credentials can be used later to create and manage additional cluster.
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Set Resources` window, select:
+
+* `Karpenter`: Toggle the switch to enable Karpenter on your AWS EKS cluster
+* `Instance types scopes`: By editing it, you can apply different filters to the node architectures, categories, families, and sizes. On the right, you can view all the instance types that match the applied filters. This means Karpenter will be able to spawn nodes on any of the listed instance types.
+  * `Architectures`: by default both `AMD64` and `ARM64` architectures are selected.
+  * `Default build architecture`: by default `AMD64`. If you build your application with the Qovery CI, your application will be built using this architecture by default.
+  * `Families`: by default all families are selected.
+  * `Sizes`: by default all sizes are selected.
+* `Spot instances`: In order to reduce even more your costs, you can also enable the spot instances on your clusters. Spot instances cost up to 90% less compared to On-Demand prices. But keep in mind that spot instances can be terminated by the cloud provider at any time. Check this [documentation](https://aws.amazon.com/ec2/spot/) for more information. Even if this flag is enabled, the statefulsets won't run on spot instances.
+* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..).
+
+<br/>
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+Please be aware that changing the instance type or disk size might cause a downtime for your service.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+Also, before downsizing, you need to ensure that your applications will still have enough resources to run correctly.
+
+</Alert>
+
+<br/>
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Features` step, select the features you want to enable on your cluster.
+
+If you want to manage the network layer of your cluster by yourself, you can switch VPC mode to `Deploy on my existing VPC` to use your own VPC instead of the one provided by Qovery.
+
+<Alert type="warning">
+
+These options can only be configured during cluster creation and cannot be modified later.
+
+</Alert>
+
+<Tabs
+  centered={true}
+  className={"rounded"}
+  defaultValue={"vpc managed by qovery"}
+  placeholder="Select a VPC mode"
+  select={false}
+  size={null}
+  values={[
+    {"group":"Features","label":"VPC managed by Qovery","value":"vpc managed by qovery"},
+    {"group":"Features","label":"Use your existing VPC","value":"use existing vpc"},
+  ]}>
+
+<TabItem value="vpc managed by qovery">
+
+#### Static IP
+
+By default, when your cluster is created, its worker nodes are allocated public IP addresses, which are used for external communication. For improved security and control, the **Static IP** feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses.
+
+Here is what will be deployed on your cluster:
+* Nat Gateways
+* Elastic IPs
+* Private subnets
+
+Once set up, here is the procedure to find your static IP addresses on `AWS`:
+- On your AWS account, select the VPC service.
+- On the left menu, you’ll find Elastic IP addresses. Once on it, in the Allocated IPv4 address column, you’ll have your public IPs.
+
+<Alert type="info">
+
+If you work in a sensitive business area such as financial technology, enabling the **Static IP** feature can help fulfil the security requirements of some of the external services you use, therefore making it easier for you to get whitelisted by them.
+
+This feature has been activated by default. Since February 1, 2024, AWS charge public IPv4 Addresses. Disabling it may cost you more, depending on the number of nodes in your cluster. Check this [link](https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/) for more information.
+
+</Alert>
+
+#### Custom VPC Subnet
+
+Virtual Private Cloud (VPC) peering allows you to set up a connection between your Qovery VPC and another VPC on your AWS account. This way, you can access resources stored on your AWS VPC directly from your Qovery applications.
+
+A VPC can only be used if it has at least one range of IP addresses called a **subnet**. When you create a cluster, Qovery automatically picks a default subnet for it. However, to perform VPC peering, you may want to define which specific VPC subnet you want to use, so that you can avoid any conflicting settings. To do so, you can enable the **Custom VPC Subnet** feature on your cluster. For more information on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
+
+</TabItem>
+
+<TabItem value="use existing vpc">
+
+You have to specify the `VPC id` (1) and ensure that in your VPC settings you have enabled the `DNS hostnames` (2):
+
+<p align="center">
+  <img src="/img/configuration/clusters/existing_vpc_aws_dns_hostnames.png" alt="Existing VPC AWS DNS Hostnmaes" />
+</p>
+
+Then you have to specify the different subnets ids:
+
+**EKS**:
+
+The EKS subnets are mandatory, you have to specify at least **one subnet id per zone** (1) and ensure you have enabled the **auto-assign public IPv4 address** setting on your subnets (2).
+
+<p align="center">
+  <img src="/img/configuration/clusters/existing_vpc_aws_auto_assign.png" alt="Existing VPC AWS DNS Hostnmaes" />
+</p>
+
+**Managed databases**:
+
+This section is exclusively for enabling managed databases (container databases will be enabled by default).
+
+Depending on the managed databases you want to you use (**MongoDB**, **RDS:MySQL/PostgreSQL** and **Redis**), specify at least one subnet id per zone.
+
+</TabItem>
+</Tabs>
+</li>
+<li>
+
+In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
+
+You can now press the `Create and Install` button.
+
+Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
+
+You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs][docs.using-qovery.configuration.clusters#logs]
+
+</li>
+</ol>
+</Steps>
+
+### Migrating from AWS with auto-scaler to AWS with Karpenter
+
+<Alert type="warning">
+
+A SQS queue will be created. Before deploying your cluster, update the IAM permissions of the Qovery user, make sure to use the [latest version here](https://hub.qovery.com/files/qovery-iam-aws.json) to add the permission on SQS.
+
+</Alert>
+
+You can easily activate Karpenter on your non-production existing cluster by following this process:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+<li>
+
+Access to `Resources` section and switch on the toggle `Activate Karpenter`
+
+</li>
+
+<li>
+
+Update your cluster by selecting the action `Update` from the drop-down menu.
+
+</li>
+
+<li>
+
+Once the update is complete, your cluster will be running on Karpenter. By default, only the instance types selected when you created your AWS cluster with the auto-scaler will be configured. You can add additional instance types by editing the instance types in the resources section.
+
+</li>
+</ol>
+</Steps>
+
+### Managing your Cluster Settings
+
+To manage the settings of an existing cluster:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+</ol>
+</Steps>
+
+Below you can find a description of each section
+
+#### General
+
+The `General` tab allows you to define high-level information on your cluster:
+
+|Item|Description|
+|--------------|---------------------------|
+|Cluster Name|To edit the name of your cluster.|
+|Description|To enter or edit the description of your cluster.|
+|Production Cluster|To enter or edit the production flag of your cluster.|
+
+#### Credentials
+
+Here you can manage here the cloud provider credentials associated with your cluster.
+
+If you need to change the credentials:
+- generate a new set of credentials on your cloud provider([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials])
+- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
+
+Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
+
+#### Resources
+
+Qovery allows you to modify the resources allocated for your cluster:
+
+- The list of the instance types
+- The spot instances activation
+- The `Node disk size (GB)` field, enter the disk capacity you want to allocate to your worker node(s) (meaning how much data, in gigabytes, you want each worker node to be able to hold).
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+</Alert>
+
+<br/>
+
+#### Image registry
+
+In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
+This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
+
+The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
+
+Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
+
+#### Features
+
+The `Features` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip),  [**Custom VPC subnet**](#custom-vpc-subnet), [**Deploy on existing VPC**](#use-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
+
+#### Network
+
+The `Network` tab in your cluster settings allows you to update your Qovery VPC route table so that you can perform VPC peering. For step-by-step guidelines on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
+
+
+[docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials]: /docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart/#attach-aws-credentials
+[docs.using-qovery.configuration.clusters#logs]: /docs/using-qovery/configuration/clusters/#logs
+[docs.using-qovery.configuration.clusters#updating-a-cluster]: /docs/using-qovery/configuration/clusters/#updating-a-cluster
+[docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]: /docs/using-qovery/configuration/clusters/#what-are-the-different-instance-types-available-when-creating-a-cluster
+[docs.using-qovery.deployment.image-mirroring]: /docs/using-qovery/deployment/image-mirroring/
+[urls.qovery_console]: https://console.qovery.com
diff --git a/website/docs/using-qovery/configuration/clusters/aws-with-karpenter.md.erb b/website/docs/using-qovery/configuration/clusters/aws-with-karpenter.md.erb
new file mode 100644
index 0000000000..a58f6689df
--- /dev/null
+++ b/website/docs/using-qovery/configuration/clusters/aws-with-karpenter.md.erb
@@ -0,0 +1,307 @@
+---
+last_modified_on: "2022-05-19"
+title: "AWS EKS with Karpenter"
+description: "Learn how to configure your AWS Kubernetes clusters with Karpenter on Qovery"
+---
+
+import Steps from '@site/src/components/Steps';
+
+import Jump from '@site/src/components/Jump';
+import Alert from '@site/src/components/Alert';
+import Assumptions from '@site/src/components/Assumptions';
+
+<Alert type="warning">
+
+Karpenter is only available for non-production clusters. If you have created a production cluster, this option will not be visible.
+
+</Alert>
+
+Karpenter automatically launches just the right compute resources to handle your cluster's applications. It is designed to let you take full advantage of the cloud with fast and simple compute provisioning for Kubernetes clusters.
+You can our [blog post](https://www.qovery.com/blog/save-up-to-60-on-aws-costs-with-eks-and-karpenter/) for more information."
+
+### Creating a AWS EKS Cluster with Karpenter
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Click on `AWS` as hosting mode and then `Qovery Managed` option:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_hosting_selection_aws.png" alt="Cluster AWS" />
+</p>
+
+In the `Create Cluster` window enter:
+
+* `Cluster name`: enter the name of your choice for your cluster.
+* `Description`: enter a description to identify better your cluster.
+* `Production cluster`: select this option if your cluster will be used for production. Note: Karpenter is currently only available for non-production clusters.
+* `Region`: select the geographical area in which you want your cluster to be hosted.
+* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials]). Added credentials can be used later to create and manage additional cluster.
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Set Resources` window, select:
+
+* `Karpenter`: Toggle the switch to enable Karpenter on your AWS EKS cluster
+* `Instance types scopes`: By editing it, you can apply different filters to the node architectures, categories, families, and sizes. On the right, you can view all the instance types that match the applied filters. This means Karpenter will be able to spawn nodes on any of the listed instance types.
+  * `Architectures`: by default both `AMD64` and `ARM64` architectures are selected.
+  * `Default build architecture`: by default `AMD64`. If you build your application with the Qovery CI, your application will be built using this architecture by default.
+  * `Families`: by default all families are selected.
+  * `Sizes`: by default all sizes are selected.
+* `Spot instances`: In order to reduce even more your costs, you can also enable the spot instances on your clusters. Spot instances cost up to 90% less compared to On-Demand prices. But keep in mind that spot instances can be terminated by the cloud provider at any time. Check this [documentation](https://aws.amazon.com/ec2/spot/) for more information. Even if this flag is enabled, the statefulsets won't run on spot instances.
+* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..).
+
+<br/>
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+Please be aware that changing the instance type or disk size might cause a downtime for your service.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+Also, before downsizing, you need to ensure that your applications will still have enough resources to run correctly.
+
+</Alert>
+
+<br/>
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Features` step, select the features you want to enable on your cluster.
+
+If you want to manage the network layer of your cluster by yourself, you can switch VPC mode to `Deploy on my existing VPC` to use your own VPC instead of the one provided by Qovery.
+
+<Alert type="warning">
+
+These options can only be configured during cluster creation and cannot be modified later.
+
+</Alert>
+
+<Tabs
+  centered={true}
+  className={"rounded"}
+  defaultValue={"vpc managed by qovery"}
+  placeholder="Select a VPC mode"
+  select={false}
+  size={null}
+  values={[
+    {"group":"Features","label":"VPC managed by Qovery","value":"vpc managed by qovery"},
+    {"group":"Features","label":"Use your existing VPC","value":"use existing vpc"},
+  ]}>
+
+<TabItem value="vpc managed by qovery">
+
+#### Static IP
+
+By default, when your cluster is created, its worker nodes are allocated public IP addresses, which are used for external communication. For improved security and control, the **Static IP** feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses.
+
+Here is what will be deployed on your cluster:
+* Nat Gateways
+* Elastic IPs
+* Private subnets
+
+Once set up, here is the procedure to find your static IP addresses on `AWS`:
+- On your AWS account, select the VPC service.
+- On the left menu, you’ll find Elastic IP addresses. Once on it, in the Allocated IPv4 address column, you’ll have your public IPs.
+
+<Alert type="info">
+
+If you work in a sensitive business area such as financial technology, enabling the **Static IP** feature can help fulfil the security requirements of some of the external services you use, therefore making it easier for you to get whitelisted by them.
+
+This feature has been activated by default. Since February 1, 2024, AWS charge public IPv4 Addresses. Disabling it may cost you more, depending on the number of nodes in your cluster. Check this [link](https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/) for more information.
+
+</Alert>
+
+#### Custom VPC Subnet
+
+Virtual Private Cloud (VPC) peering allows you to set up a connection between your Qovery VPC and another VPC on your AWS account. This way, you can access resources stored on your AWS VPC directly from your Qovery applications.
+
+A VPC can only be used if it has at least one range of IP addresses called a **subnet**. When you create a cluster, Qovery automatically picks a default subnet for it. However, to perform VPC peering, you may want to define which specific VPC subnet you want to use, so that you can avoid any conflicting settings. To do so, you can enable the **Custom VPC Subnet** feature on your cluster. For more information on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
+
+</TabItem>
+
+<TabItem value="use existing vpc">
+
+You have to specify the `VPC id` (1) and ensure that in your VPC settings you have enabled the `DNS hostnames` (2):
+
+<p align="center">
+  <img src="/img/configuration/clusters/existing_vpc_aws_dns_hostnames.png" alt="Existing VPC AWS DNS Hostnmaes" />
+</p>
+
+Then you have to specify the different subnets ids:
+
+**EKS**:
+
+The EKS subnets are mandatory, you have to specify at least **one subnet id per zone** (1) and ensure you have enabled the **auto-assign public IPv4 address** setting on your subnets (2).
+
+<p align="center">
+  <img src="/img/configuration/clusters/existing_vpc_aws_auto_assign.png" alt="Existing VPC AWS DNS Hostnmaes" />
+</p>
+
+**Managed databases**:
+
+This section is exclusively for enabling managed databases (container databases will be enabled by default).
+
+Depending on the managed databases you want to you use (**MongoDB**, **RDS:MySQL/PostgreSQL** and **Redis**), specify at least one subnet id per zone.
+
+</TabItem>
+</Tabs>
+</li>
+<li>
+
+In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
+
+You can now press the `Create and Install` button.
+
+Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
+
+You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs][docs.using-qovery.configuration.clusters#logs]
+
+</li>
+</ol>
+</Steps>
+
+### Migrating from AWS with auto-scaler to AWS with Karpenter
+
+<Alert type="warning">
+
+A SQS queue will be created. Before deploying your cluster, update the IAM permissions of the Qovery user, make sure to use the [latest version here](https://hub.qovery.com/files/qovery-iam-aws.json) to add the permission on SQS.
+
+</Alert>
+
+You can easily activate Karpenter on your non-production existing cluster by following this process:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+<li>
+
+Access to `Resources` section and switch on the toggle `Activate Karpenter`
+
+</li>
+
+<li>
+
+Update your cluster by selecting the action `Update` from the drop-down menu.
+
+</li>
+
+<li>
+
+Once the update is complete, your cluster will be running on Karpenter. By default, only the instance types selected when you created your AWS cluster with the auto-scaler will be configured. You can add additional instance types by editing the instance types in the resources section.
+
+</li>
+</ol>
+</Steps>
+
+### Managing your Cluster Settings
+
+To manage the settings of an existing cluster:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+</ol>
+</Steps>
+
+Below you can find a description of each section
+
+#### General
+
+The `General` tab allows you to define high-level information on your cluster:
+
+|Item|Description|
+|--------------|---------------------------|
+|Cluster Name|To edit the name of your cluster.|
+|Description|To enter or edit the description of your cluster.|
+|Production Cluster|To enter or edit the production flag of your cluster.|
+
+#### Credentials
+
+Here you can manage here the cloud provider credentials associated with your cluster.
+
+If you need to change the credentials:
+- generate a new set of credentials on your cloud provider([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials])
+- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
+
+Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
+
+#### Resources
+
+Qovery allows you to modify the resources allocated for your cluster:
+
+- The list of the instance types
+- The spot instances activation
+- The `Node disk size (GB)` field, enter the disk capacity you want to allocate to your worker node(s) (meaning how much data, in gigabytes, you want each worker node to be able to hold).
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+</Alert>
+
+<br/>
+
+#### Image registry
+
+In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
+This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
+
+The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
+
+Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
+
+#### Features
+
+The `Features` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip),  [**Custom VPC subnet**](#custom-vpc-subnet), [**Deploy on existing VPC**](#use-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
+
+#### Network
+
+The `Network` tab in your cluster settings allows you to update your Qovery VPC route table so that you can perform VPC peering. For step-by-step guidelines on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
\ No newline at end of file
diff --git a/website/docs/using-qovery/configuration/clusters/aws.md b/website/docs/using-qovery/configuration/clusters/aws.md
new file mode 100644
index 0000000000..fe4ddb086a
--- /dev/null
+++ b/website/docs/using-qovery/configuration/clusters/aws.md
@@ -0,0 +1,277 @@
+---
+last_modified_on: "2024-11-27"
+title: "AWS EKS"
+description: "Learn how to configure your AWS Kubernetes clusters on Qovery"
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+import Steps from '@site/src/components/Steps';
+
+import Jump from '@site/src/components/Jump';
+import Alert from '@site/src/components/Alert';
+import Assumptions from '@site/src/components/Assumptions';
+
+<Alert type="info">
+
+By default, clusters will be deployed with the AWS default autoscaler. If you are looking to install Qovery on your AWS cluster with the Karpenter autoscaler to improve cluster resource usage and activate spot instances, please refer to [this guide][docs.using-qovery.configuration.clusters.aws-with-karpenter].
+
+<Alert type="warning">
+
+Karpenter is only available for non-production clusters. If you have created a production cluster, this option will not be visible.
+
+</Alert>
+
+</Alert>
+
+### Creating a AWS EKS Cluster
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Click on `AWS` as hosting mode and then `Qovery Managed` option:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_hosting_selection_aws.png" alt="Cluster AWS" />
+</p>
+
+In the `Create Cluster` window enter:
+
+* `Cluster name`: enter the name of your choice for your cluster.
+* `Description`: enter a description to identify better your cluster.
+* `Production cluster`: select this option if your cluster will be used for production.
+* `Region`: select the geographical area in which you want your cluster to be hosted.
+* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials]). Added credentials can be used later to create and manage additional cluster.
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Set Resources` window, select:
+
+* `Karpenter`: to activate karpenter. If you are looking to install Qovery on your AWS with Karpenter, please refer to [this guide][docs.using-qovery.configuration.clusters.aws-with-karpenter]
+* `Instance type`: select the type of [worker nodes][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster.
+* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..).
+* `Node auto-scaling`: define the minimum and the maximum number of worker nodes that your cluster can run. The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows. Please note that a minimum of 3 worker nodes is required to deploy your EKS cluster.
+
+<br/>
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+Please be aware that changing the instance type or disk size might cause a downtime for your service.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+Also, before downsizing, you need to ensure that your applications will still have enough resources to run correctly.
+
+</Alert>
+
+<br/>
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Features` step, select the features you want to enable on your cluster.
+
+If you want to manage the network layer of your cluster by yourself, you can switch VPC mode to `Deploy on my existing VPC` to use your own VPC instead of the one provided by Qovery.
+
+<Alert type="warning">
+
+These options can only be configured during cluster creation and cannot be modified later.
+
+</Alert>
+
+<Tabs
+  centered={true}
+  className={"rounded"}
+  defaultValue={"vpc managed by qovery"}
+  placeholder="Select a VPC mode"
+  select={false}
+  size={null}
+  values={[
+    {"group":"Features","label":"VPC managed by Qovery","value":"vpc managed by qovery"},
+    {"group":"Features","label":"Use your existing VPC","value":"use existing vpc"},
+  ]}>
+
+<TabItem value="vpc managed by qovery">
+
+#### Static IP
+
+By default, when your cluster is created, its worker nodes are allocated public IP addresses, which are used for external communication. For improved security and control, the **Static IP** feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses.
+
+Here is what will be deployed on your cluster:
+* Nat Gateways
+* Elastic IPs
+* Private subnets
+
+Once set up, here is the procedure to find your static IP addresses on `AWS`:
+- On your AWS account, select the VPC service.
+- On the left menu, you’ll find Elastic IP addresses. Once on it, in the Allocated IPv4 address column, you’ll have your public IPs.
+
+<Alert type="info">
+
+If you work in a sensitive business area such as financial technology, enabling the **Static IP** feature can help fulfil the security requirements of some of the external services you use, therefore making it easier for you to get whitelisted by them.
+
+This feature has been activated by default. Since February 1, 2024, AWS charge public IPv4 Addresses. Disabling it may cost you more, depending on the number of nodes in your cluster. Check this [link](https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/) for more information.
+
+</Alert>
+
+#### Custom VPC Subnet
+
+Virtual Private Cloud (VPC) peering allows you to set up a connection between your Qovery VPC and another VPC on your AWS account. This way, you can access resources stored on your AWS VPC directly from your Qovery applications.
+
+A VPC can only be used if it has at least one range of IP addresses called a **subnet**. When you create a cluster, Qovery automatically picks a default subnet for it. However, to perform VPC peering, you may want to define which specific VPC subnet you want to use, so that you can avoid any conflicting settings. To do so, you can enable the **Custom VPC Subnet** feature on your cluster. For more information on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
+
+</TabItem>
+
+<TabItem value="use existing vpc">
+
+You have to specify the `VPC id` (1) and ensure that in your VPC settings you have enabled the `DNS hostnames` (2):
+
+<p align="center">
+  <img src="/img/configuration/clusters/existing_vpc_aws_dns_hostnames.png" alt="Existing VPC AWS DNS Hostnmaes" />
+</p>
+
+Then you have to specify the different subnets ids:
+
+**EKS**:
+
+The EKS subnets are mandatory, you have to specify at least **one subnet id per zone** (1) and ensure you have enabled the **auto-assign public IPv4 address** setting on your subnets (2).
+
+<p align="center">
+  <img src="/img/configuration/clusters/existing_vpc_aws_auto_assign.png" alt="Existing VPC AWS DNS Hostnmaes" />
+</p>
+
+**Managed databases**:
+
+This section is exclusively for enabling managed databases (container databases will be enabled by default).
+
+Depending on the managed databases you want to you use (**MongoDB**, **RDS:MySQL/PostgreSQL** and **Redis**), specify at least one subnet id per zone.
+
+</TabItem>
+</Tabs>
+</li>
+<li>
+
+In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
+
+You can now press the `Create and Install` button.
+
+Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
+
+You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs][docs.using-qovery.configuration.clusters#logs]
+
+</li>
+</ol>
+</Steps>
+
+
+### Managing your Cluster Settings
+
+To manage the settings of an existing cluster:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+</ol>
+</Steps>
+
+Below you can find a description of each section
+
+#### General
+
+The `General` tab allows you to define high-level information on your cluster:
+
+|Item|Description|
+|--------------|---------------------------|
+|Cluster Name|To edit the name of your cluster.|
+|Description|To enter or edit the description of your cluster.|
+|Production Cluster|To enter or edit the production flag of your cluster.|
+
+#### Credentials
+
+Here you can manage here the cloud provider credentials associated with your cluster.
+
+If you need to change the credentials:
+- generate a new set of credentials on your cloud provider([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials])
+- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
+
+Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
+
+#### Resources
+
+Qovery allows you to modify the resources allocated for your cluster:
+
+- In the `Instance type` dropdown menu, select the type of [worker node(s)][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster.
+- *(AWS users only)* In the `Node disk size (GB)` field, enter the disk capacity you want to allocate to your worker node(s) (meaning how much data, in gigabytes, you want each worker node to be able to hold).
+- *(EKS users only)* On the `Nodes auto-scaling`, define the range of worker nodes you want to deploy to your cluster.
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+</Alert>
+
+<br/>
+
+<Alert type="info">
+
+The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows.
+
+Please note that a minimum of 3 worker nodes is required to deploy your [EKS cluster][docs.using-qovery.configuration.clusters#creating-a-cluster].
+
+</Alert>
+
+#### Image registry
+
+In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
+This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
+
+The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
+
+Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
+
+#### Features
+
+The `Features` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip),  [**Custom VPC subnet**](#custom-vpc-subnet), [**Deploy on existing VPC**](#use-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
+
+#### Network
+
+The `Network` tab in your cluster settings allows you to update your Qovery VPC route table so that you can perform VPC peering. For step-by-step guidelines on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
+
+
+[docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials]: /docs/getting-started/install-qovery/aws/cluster-managed-by-qovery/quickstart/#attach-aws-credentials
+[docs.using-qovery.configuration.clusters#creating-a-cluster]: /docs/using-qovery/configuration/clusters/#creating-a-cluster
+[docs.using-qovery.configuration.clusters#logs]: /docs/using-qovery/configuration/clusters/#logs
+[docs.using-qovery.configuration.clusters#updating-a-cluster]: /docs/using-qovery/configuration/clusters/#updating-a-cluster
+[docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]: /docs/using-qovery/configuration/clusters/#what-are-the-different-instance-types-available-when-creating-a-cluster
+[docs.using-qovery.configuration.clusters#what-is-a-cluster]: /docs/using-qovery/configuration/clusters/#what-is-a-cluster
+[docs.using-qovery.configuration.clusters.aws-with-karpenter]: /docs/using-qovery/configuration/clusters/aws-with-karpenter/
+[docs.using-qovery.deployment.image-mirroring]: /docs/using-qovery/deployment/image-mirroring/
+[urls.qovery_console]: https://console.qovery.com
diff --git a/website/docs/using-qovery/configuration/clusters/aws.md.erb b/website/docs/using-qovery/configuration/clusters/aws.md.erb
new file mode 100644
index 0000000000..31cab64b01
--- /dev/null
+++ b/website/docs/using-qovery/configuration/clusters/aws.md.erb
@@ -0,0 +1,263 @@
+---
+last_modified_on: "2022-05-19"
+title: "AWS EKS"
+description: "Learn how to configure your AWS Kubernetes clusters on Qovery"
+---
+
+import Steps from '@site/src/components/Steps';
+
+import Jump from '@site/src/components/Jump';
+import Alert from '@site/src/components/Alert';
+import Assumptions from '@site/src/components/Assumptions';
+
+<Alert type="info">
+
+By default, clusters will be deployed with the AWS default autoscaler. If you are looking to install Qovery on your AWS cluster with the Karpenter autoscaler to improve cluster resource usage and activate spot instances, please refer to [this guide][docs.using-qovery.configuration.clusters.aws-with-karpenter].
+
+<Alert type="warning">
+
+Karpenter is only available for non-production clusters. If you have created a production cluster, this option will not be visible.
+
+</Alert>
+
+</Alert>
+
+### Creating a AWS EKS Cluster
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Click on `AWS` as hosting mode and then `Qovery Managed` option:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_hosting_selection_aws.png" alt="Cluster AWS" />
+</p>
+
+In the `Create Cluster` window enter:
+
+* `Cluster name`: enter the name of your choice for your cluster.
+* `Description`: enter a description to identify better your cluster.
+* `Production cluster`: select this option if your cluster will be used for production.
+* `Region`: select the geographical area in which you want your cluster to be hosted.
+* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials]). Added credentials can be used later to create and manage additional cluster.
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Set Resources` window, select:
+
+* `Karpenter`: to activate karpenter. If you are looking to install Qovery on your AWS with Karpenter, please refer to [this guide][docs.using-qovery.configuration.clusters.aws-with-karpenter]
+* `Instance type`: select the type of [worker nodes][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster.
+* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..).
+* `Node auto-scaling`: define the minimum and the maximum number of worker nodes that your cluster can run. The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows. Please note that a minimum of 3 worker nodes is required to deploy your EKS cluster.
+
+<br/>
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+Please be aware that changing the instance type or disk size might cause a downtime for your service.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+Also, before downsizing, you need to ensure that your applications will still have enough resources to run correctly.
+
+</Alert>
+
+<br/>
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Features` step, select the features you want to enable on your cluster.
+
+If you want to manage the network layer of your cluster by yourself, you can switch VPC mode to `Deploy on my existing VPC` to use your own VPC instead of the one provided by Qovery.
+
+<Alert type="warning">
+
+These options can only be configured during cluster creation and cannot be modified later.
+
+</Alert>
+
+<Tabs
+  centered={true}
+  className={"rounded"}
+  defaultValue={"vpc managed by qovery"}
+  placeholder="Select a VPC mode"
+  select={false}
+  size={null}
+  values={[
+    {"group":"Features","label":"VPC managed by Qovery","value":"vpc managed by qovery"},
+    {"group":"Features","label":"Use your existing VPC","value":"use existing vpc"},
+  ]}>
+
+<TabItem value="vpc managed by qovery">
+
+#### Static IP
+
+By default, when your cluster is created, its worker nodes are allocated public IP addresses, which are used for external communication. For improved security and control, the **Static IP** feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses.
+
+Here is what will be deployed on your cluster:
+* Nat Gateways
+* Elastic IPs
+* Private subnets
+
+Once set up, here is the procedure to find your static IP addresses on `AWS`:
+- On your AWS account, select the VPC service.
+- On the left menu, you’ll find Elastic IP addresses. Once on it, in the Allocated IPv4 address column, you’ll have your public IPs.
+
+<Alert type="info">
+
+If you work in a sensitive business area such as financial technology, enabling the **Static IP** feature can help fulfil the security requirements of some of the external services you use, therefore making it easier for you to get whitelisted by them.
+
+This feature has been activated by default. Since February 1, 2024, AWS charge public IPv4 Addresses. Disabling it may cost you more, depending on the number of nodes in your cluster. Check this [link](https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/) for more information.
+
+</Alert>
+
+#### Custom VPC Subnet
+
+Virtual Private Cloud (VPC) peering allows you to set up a connection between your Qovery VPC and another VPC on your AWS account. This way, you can access resources stored on your AWS VPC directly from your Qovery applications.
+
+A VPC can only be used if it has at least one range of IP addresses called a **subnet**. When you create a cluster, Qovery automatically picks a default subnet for it. However, to perform VPC peering, you may want to define which specific VPC subnet you want to use, so that you can avoid any conflicting settings. To do so, you can enable the **Custom VPC Subnet** feature on your cluster. For more information on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
+
+</TabItem>
+
+<TabItem value="use existing vpc">
+
+You have to specify the `VPC id` (1) and ensure that in your VPC settings you have enabled the `DNS hostnames` (2):
+
+<p align="center">
+  <img src="/img/configuration/clusters/existing_vpc_aws_dns_hostnames.png" alt="Existing VPC AWS DNS Hostnmaes" />
+</p>
+
+Then you have to specify the different subnets ids:
+
+**EKS**:
+
+The EKS subnets are mandatory, you have to specify at least **one subnet id per zone** (1) and ensure you have enabled the **auto-assign public IPv4 address** setting on your subnets (2).
+
+<p align="center">
+  <img src="/img/configuration/clusters/existing_vpc_aws_auto_assign.png" alt="Existing VPC AWS DNS Hostnmaes" />
+</p>
+
+**Managed databases**:
+
+This section is exclusively for enabling managed databases (container databases will be enabled by default).
+
+Depending on the managed databases you want to you use (**MongoDB**, **RDS:MySQL/PostgreSQL** and **Redis**), specify at least one subnet id per zone.
+
+</TabItem>
+</Tabs>
+</li>
+<li>
+
+In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
+
+You can now press the `Create and Install` button.
+
+Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
+
+You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs][docs.using-qovery.configuration.clusters#logs]
+
+</li>
+</ol>
+</Steps>
+
+
+### Managing your Cluster Settings
+
+To manage the settings of an existing cluster:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+</ol>
+</Steps>
+
+Below you can find a description of each section
+
+#### General
+
+The `General` tab allows you to define high-level information on your cluster:
+
+|Item|Description|
+|--------------|---------------------------|
+|Cluster Name|To edit the name of your cluster.|
+|Description|To enter or edit the description of your cluster.|
+|Production Cluster|To enter or edit the production flag of your cluster.|
+
+#### Credentials
+
+Here you can manage here the cloud provider credentials associated with your cluster.
+
+If you need to change the credentials:
+- generate a new set of credentials on your cloud provider([Procedure for AWS account][docs.getting-started.install-qovery.aws.cluster-managed-by-qovery.quickstart#attach-aws-credentials])
+- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
+
+Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
+
+#### Resources
+
+Qovery allows you to modify the resources allocated for your cluster:
+
+- In the `Instance type` dropdown menu, select the type of [worker node(s)][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster.
+- *(AWS users only)* In the `Node disk size (GB)` field, enter the disk capacity you want to allocate to your worker node(s) (meaning how much data, in gigabytes, you want each worker node to be able to hold).
+- *(EKS users only)* On the `Nodes auto-scaling`, define the range of worker nodes you want to deploy to your cluster.
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+</Alert>
+
+<br/>
+
+<Alert type="info">
+
+The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows.
+
+Please note that a minimum of 3 worker nodes is required to deploy your [EKS cluster][docs.using-qovery.configuration.clusters#creating-a-cluster].
+
+</Alert>
+
+#### Image registry
+
+In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
+This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
+
+The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
+
+Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
+
+#### Features
+
+The `Features` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip),  [**Custom VPC subnet**](#custom-vpc-subnet), [**Deploy on existing VPC**](#use-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
+
+#### Network
+
+The `Network` tab in your cluster settings allows you to update your Qovery VPC route table so that you can perform VPC peering. For step-by-step guidelines on how to set up VPC peering, [see our dedicated tutorial](https://hub.qovery.com/guides/tutorial/aws-vpc-peering-with-qovery/).
\ No newline at end of file
diff --git a/website/docs/using-qovery/configuration/clusters/gcp.md b/website/docs/using-qovery/configuration/clusters/gcp.md
new file mode 100644
index 0000000000..5b1548c4c0
--- /dev/null
+++ b/website/docs/using-qovery/configuration/clusters/gcp.md
@@ -0,0 +1,200 @@
+---
+last_modified_on: "2024-11-27"
+title: "GCP GKE"
+description: "Learn how to configure your GCP Kubernetes clusters on Qovery"
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+import Steps from '@site/src/components/Steps';
+
+import Jump from '@site/src/components/Jump';
+import Alert from '@site/src/components/Alert';
+import Assumptions from '@site/src/components/Assumptions';
+
+### Creating a GCP GKE Cluster
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Click on `GCP` as hosting mode and then `Qovery Managed` option:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_hosting_selection_gcp.png" alt="Cluster GCP" />
+</p>
+
+
+In the `Create Cluster` window enter:
+
+* `Cluster name`: enter the name of your choice for your cluster.
+* `Description`: enter a description to identify better your cluster.
+* `Production cluster`: select this option if your cluster will be used for production.
+* `Region`: select the geographical area in which you want your cluster to be hosted.
+* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for GCP account][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials]). Added credentials can be used later to create and manage additional cluster.
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Features` step, select the features you want to enable on your cluster.
+
+If you want to manage the network layer of your cluster by yourself, you can switch VPC mode to `Deploy on my existing VPC` to use your own VPC instead of the one provided by Qovery.
+
+<Alert type="warning">
+
+These options can only be configured during cluster creation and cannot be modified later.
+
+</Alert>
+
+<Tabs
+  centered={true}
+  className={"rounded"}
+  defaultValue={"vpc managed by qovery"}
+  placeholder="Select a VPC mode"
+  select={false}
+  size={null}
+  values={[
+    {"group":"Features","label":"VPC managed by Qovery","value":"vpc managed by qovery"},
+    {"group":"Features","label":"Use your existing VPC","value":"use existing vpc"},
+  ]}>
+
+<TabItem value="vpc managed by qovery">
+
+#### Static IP
+
+The **Static IP** feature is currently only available to clusters deployed with a VPC managed by Qovery and can only be enabled at cluster creation.
+
+By default, when your cluster is created, its worker nodes are allocated public IP addresses, which are used for external communication. For improved security and control, the **Static IP** feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses.
+
+Here is what will be deployed on your cluster:
+* Cloud Nats
+* Static IPs
+* Routers
+
+Once set up, here is the procedure to find your static IP addresses on `GCP`:
+- On your GCP account, select the IP addresses service.
+- In the list you will find your static IP used by your cluster router.
+
+<Alert type="info">
+
+If you work in a sensitive business area such as financial technology, enabling the **Static IP** feature can help fulfil the security requirements of some of the external services you use, therefore making it easier for you to get whitelisted by them.
+
+</Alert>
+
+</TabItem>
+
+<TabItem value="use existing vpc">
+
+##### Use existing VPC
+
+You can opt to use your own VPC instead of the one provided by Qovery by switching VPC mode to `Deploy on my existing VPC`.
+
+In GCP you have two VPC modes: `Automatic` or `Custom`.
+
+If you are using an automatic or a custom VPC, you have to set:
+* Your VPC Name
+* External project id (optional): by default, the project id used is the one specified in the credentials file. But if your VPC is defined in another GCP project, you have to specify the Project id.
+
+In addition if you are using a custom VPC, you have to set:
+* Your Subnet range name (`https://console.cloud.google.com/networking/networks/details/<your-vpc>?project=<your-project>&pageTab=SUBNETS`)
+
+<Alert type="info">
+
+You can also specify (optional):
+  * Pod ipv4 address range name
+  * Additional cluster pod ipv4 ranges names (separated with a comma)
+  * Ipv4 service range name
+
+For these ranges, you have to create Secondary IPv4 ranges inside your subnet.
+
+</Alert>
+</TabItem>
+</Tabs>
+</li>
+<li>
+
+In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
+
+You can now press the `Create and Install` button.
+
+Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
+
+You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs][docs.using-qovery.configuration.clusters#logs]
+
+</li>
+</ol>
+</Steps>
+
+
+### Managing your Cluster Settings
+
+To manage the settings of an existing cluster:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+</ol>
+</Steps>
+
+Below you can find a description of each section
+
+#### General
+
+The `General` tab allows you to define high-level information on your cluster:
+
+|Item|Description|
+|--------------|---------------------------|
+|Cluster Name|To edit the name of your cluster.|
+|Description|To enter or edit the description of your cluster.|
+|Production Cluster|To enter or edit the production flag of your cluster.|
+
+#### Credentials
+
+Here you can manage here the cloud provider credentials associated with your cluster.
+
+If you need to change the credentials:
+- generate a new set of credentials on your cloud provider([Procedure for GCP account][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials])
+- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
+
+Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
+
+#### Image registry
+
+In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
+This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
+
+The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
+
+Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
+
+#### Features
+
+The `Features` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip), [**Deploy on existing VPC**](#use-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
+
+
+[docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials]: /docs/getting-started/install-qovery/gcp/cluster-managed-by-qovery/quickstart/#attach-gcp-credentials
+[docs.using-qovery.configuration.clusters#logs]: /docs/using-qovery/configuration/clusters/#logs
+[docs.using-qovery.configuration.clusters#updating-a-cluster]: /docs/using-qovery/configuration/clusters/#updating-a-cluster
+[docs.using-qovery.deployment.image-mirroring]: /docs/using-qovery/deployment/image-mirroring/
+[urls.qovery_console]: https://console.qovery.com
diff --git a/website/docs/using-qovery/configuration/clusters/gcp.md.erb b/website/docs/using-qovery/configuration/clusters/gcp.md.erb
new file mode 100644
index 0000000000..1cf5096b6e
--- /dev/null
+++ b/website/docs/using-qovery/configuration/clusters/gcp.md.erb
@@ -0,0 +1,190 @@
+---
+last_modified_on: "2022-05-19"
+title: "GCP GKE"
+description: "Learn how to configure your GCP Kubernetes clusters on Qovery"
+---
+
+import Steps from '@site/src/components/Steps';
+
+import Jump from '@site/src/components/Jump';
+import Alert from '@site/src/components/Alert';
+import Assumptions from '@site/src/components/Assumptions';
+
+### Creating a GCP GKE Cluster
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Click on `GCP` as hosting mode and then `Qovery Managed` option:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_hosting_selection_gcp.png" alt="Cluster GCP" />
+</p>
+
+
+In the `Create Cluster` window enter:
+
+* `Cluster name`: enter the name of your choice for your cluster.
+* `Description`: enter a description to identify better your cluster.
+* `Production cluster`: select this option if your cluster will be used for production.
+* `Region`: select the geographical area in which you want your cluster to be hosted.
+* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for GCP account][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials]). Added credentials can be used later to create and manage additional cluster.
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Features` step, select the features you want to enable on your cluster.
+
+If you want to manage the network layer of your cluster by yourself, you can switch VPC mode to `Deploy on my existing VPC` to use your own VPC instead of the one provided by Qovery.
+
+<Alert type="warning">
+
+These options can only be configured during cluster creation and cannot be modified later.
+
+</Alert>
+
+<Tabs
+  centered={true}
+  className={"rounded"}
+  defaultValue={"vpc managed by qovery"}
+  placeholder="Select a VPC mode"
+  select={false}
+  size={null}
+  values={[
+    {"group":"Features","label":"VPC managed by Qovery","value":"vpc managed by qovery"},
+    {"group":"Features","label":"Use your existing VPC","value":"use existing vpc"},
+  ]}>
+
+<TabItem value="vpc managed by qovery">
+
+#### Static IP
+
+The **Static IP** feature is currently only available to clusters deployed with a VPC managed by Qovery and can only be enabled at cluster creation.
+
+By default, when your cluster is created, its worker nodes are allocated public IP addresses, which are used for external communication. For improved security and control, the **Static IP** feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses.
+
+Here is what will be deployed on your cluster:
+* Cloud Nats
+* Static IPs
+* Routers
+
+Once set up, here is the procedure to find your static IP addresses on `GCP`:
+- On your GCP account, select the IP addresses service.
+- In the list you will find your static IP used by your cluster router.
+
+<Alert type="info">
+
+If you work in a sensitive business area such as financial technology, enabling the **Static IP** feature can help fulfil the security requirements of some of the external services you use, therefore making it easier for you to get whitelisted by them.
+
+</Alert>
+
+</TabItem>
+
+<TabItem value="use existing vpc">
+
+##### Use existing VPC
+
+You can opt to use your own VPC instead of the one provided by Qovery by switching VPC mode to `Deploy on my existing VPC`.
+
+In GCP you have two VPC modes: `Automatic` or `Custom`.
+
+If you are using an automatic or a custom VPC, you have to set:
+* Your VPC Name
+* External project id (optional): by default, the project id used is the one specified in the credentials file. But if your VPC is defined in another GCP project, you have to specify the Project id.
+
+In addition if you are using a custom VPC, you have to set:
+* Your Subnet range name (`https://console.cloud.google.com/networking/networks/details/<your-vpc>?project=<your-project>&pageTab=SUBNETS`)
+
+<Alert type="info">
+
+You can also specify (optional):
+  * Pod ipv4 address range name
+  * Additional cluster pod ipv4 ranges names (separated with a comma)
+  * Ipv4 service range name
+
+For these ranges, you have to create Secondary IPv4 ranges inside your subnet.
+
+</Alert>
+</TabItem>
+</Tabs>
+</li>
+<li>
+
+In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
+
+You can now press the `Create and Install` button.
+
+Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
+
+You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs][docs.using-qovery.configuration.clusters#logs]
+
+</li>
+</ol>
+</Steps>
+
+
+### Managing your Cluster Settings
+
+To manage the settings of an existing cluster:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+</ol>
+</Steps>
+
+Below you can find a description of each section
+
+#### General
+
+The `General` tab allows you to define high-level information on your cluster:
+
+|Item|Description|
+|--------------|---------------------------|
+|Cluster Name|To edit the name of your cluster.|
+|Description|To enter or edit the description of your cluster.|
+|Production Cluster|To enter or edit the production flag of your cluster.|
+
+#### Credentials
+
+Here you can manage here the cloud provider credentials associated with your cluster.
+
+If you need to change the credentials:
+- generate a new set of credentials on your cloud provider([Procedure for GCP account][docs.getting-started.install-qovery.gcp.cluster-managed-by-qovery.quickstart#attach-gcp-credentials])
+- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
+
+Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
+
+#### Image registry
+
+In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
+This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
+
+The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
+
+Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
+
+#### Features
+
+The `Features` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip), [**Deploy on existing VPC**](#use-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
\ No newline at end of file
diff --git a/website/docs/using-qovery/configuration/clusters/scaleway.md b/website/docs/using-qovery/configuration/clusters/scaleway.md
new file mode 100644
index 0000000000..50fe2a49c0
--- /dev/null
+++ b/website/docs/using-qovery/configuration/clusters/scaleway.md
@@ -0,0 +1,145 @@
+---
+last_modified_on: "2024-11-27"
+title: "Scaleway kapsule"
+description: "Learn how to configure your Scaleway Kubernetes clusters on Qovery"
+---
+
+import Steps from '@site/src/components/Steps';
+
+import Jump from '@site/src/components/Jump';
+import Alert from '@site/src/components/Alert';
+import Assumptions from '@site/src/components/Assumptions';
+
+### Creating a Scaleway Kapsule Cluster
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Click on `Scaleway` as hosting mode and then `Qovery Managed` option:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_hosting_selection_scw.png" alt="Cluster Scaleway" />
+</p>
+
+
+In the `Create Cluster` window enter:
+
+* `Cluster name`: enter the name of your choice for your cluster.
+* `Description`: enter a description to identify better your cluster.
+* `Production cluster`: select this option if your cluster will be used for production.
+* `Region`: select the geographical area in which you want your cluster to be hosted.
+* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for Scaleway account][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials]). Added credentials can be used later to create and manage additional cluster.
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Set Resources` window, select:
+
+* `Instance type`: select the type of [worker nodes][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster.
+* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..).
+* `Node auto-scaling`: define the minimum and the maximum number of worker nodes that your cluster can run. The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows. Please note that a minimum of 3 worker nodes is required to deploy your EKS cluster.
+
+<br/>
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+Please be aware that changing the instance type or disk size might cause a downtime for your service.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+Also, before downsizing, you need to ensure that your applications will still have enough resources to run correctly.
+
+</Alert>
+
+<br/>
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
+
+You can now press the `Create and Install` button.
+
+Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
+
+You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs][docs.using-qovery.configuration.clusters#logs]
+
+</li>
+</ol>
+</Steps>
+
+
+### Managing your Cluster Settings
+
+To manage the settings of an existing cluster:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+</ol>
+</Steps>
+
+Below you can find a description of each section
+
+#### General
+
+The `General` tab allows you to define high-level information on your cluster:
+
+|Item|Description|
+|--------------|---------------------------|
+|Cluster Name|To edit the name of your cluster.|
+|Description|To enter or edit the description of your cluster.|
+|Production Cluster|To enter or edit the production flag of your cluster.|
+
+#### Credentials
+
+Here you can manage here the cloud provider credentials associated with your cluster.
+
+If you need to change the credentials:
+- generate a new set of credentials on your cloud provider([Procedure for Scaleway account][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials])
+- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
+
+Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
+
+#### Image registry
+
+In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
+This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
+
+The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
+
+Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
+
+
+[docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials]: /docs/getting-started/install-qovery/scaleway/cluster-managed-by-qovery/quickstart/#attach-scaleway-credentials
+[docs.using-qovery.configuration.clusters#logs]: /docs/using-qovery/configuration/clusters/#logs
+[docs.using-qovery.configuration.clusters#updating-a-cluster]: /docs/using-qovery/configuration/clusters/#updating-a-cluster
+[docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]: /docs/using-qovery/configuration/clusters/#what-are-the-different-instance-types-available-when-creating-a-cluster
+[docs.using-qovery.configuration.clusters#what-is-a-cluster]: /docs/using-qovery/configuration/clusters/#what-is-a-cluster
+[docs.using-qovery.deployment.image-mirroring]: /docs/using-qovery/deployment/image-mirroring/
+[urls.qovery_console]: https://console.qovery.com
diff --git a/website/docs/using-qovery/configuration/clusters/scaleway.md.erb b/website/docs/using-qovery/configuration/clusters/scaleway.md.erb
new file mode 100644
index 0000000000..1eb49561d6
--- /dev/null
+++ b/website/docs/using-qovery/configuration/clusters/scaleway.md.erb
@@ -0,0 +1,136 @@
+---
+last_modified_on: "2022-05-19"
+title: "Scaleway kapsule"
+description: "Learn how to configure your Scaleway Kubernetes clusters on Qovery"
+---
+
+import Steps from '@site/src/components/Steps';
+
+import Jump from '@site/src/components/Jump';
+import Alert from '@site/src/components/Alert';
+import Assumptions from '@site/src/components/Assumptions';
+
+### Creating a Scaleway Kapsule Cluster
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Click on `Scaleway` as hosting mode and then `Qovery Managed` option:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_hosting_selection_scw.png" alt="Cluster Scaleway" />
+</p>
+
+
+In the `Create Cluster` window enter:
+
+* `Cluster name`: enter the name of your choice for your cluster.
+* `Description`: enter a description to identify better your cluster.
+* `Production cluster`: select this option if your cluster will be used for production.
+* `Region`: select the geographical area in which you want your cluster to be hosted.
+* `Credentials`: select one of the existing cloud provider credentials or add a new one by clicking on `New Credentials`. In the New credentials window, add the credentials that you have generated on your cloud provider console ([Procedure for Scaleway account][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials]). Added credentials can be used later to create and manage additional cluster.
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Set Resources` window, select:
+
+* `Instance type`: select the type of [worker nodes][docs.using-qovery.configuration.clusters#what-is-a-cluster] you want to deploy to your cluster.
+* `Disk size`: select the size of the disks to be attached to your cluster instances (to locally store container images etc..).
+* `Node auto-scaling`: define the minimum and the maximum number of worker nodes that your cluster can run. The lowest number is the number of worker nodes running on your infrastructure at any time, while the highest number is the maximum number of worker nodes that can automatically be deployed as traffic grows. Please note that a minimum of 3 worker nodes is required to deploy your EKS cluster.
+
+<br/>
+
+<Alert type="warning">
+Instance type selection from your Qovery Console has direct consequences on your cloud provider’s bill. While Qovery allows you to switch to a different instance type whenever you want, it is your sole responsibility to keep an eye on your infrastructure costs, especially when you want to upsize.
+
+Please be aware that changing the instance type or disk size might cause a downtime for your service.
+
+For more information on the instance types provided by each cloud provider and their associated pricing, see [What are the different instance types available when creating a cluster?][docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]
+
+Also, before downsizing, you need to ensure that your applications will still have enough resources to run correctly.
+
+</Alert>
+
+<br/>
+
+To confirm, click `Next`.
+
+</li>
+<li>
+
+In the `Ready to install your cluster` window, check that the services needed to install your cluster are correct.
+
+You can now press the `Create and Install` button.
+
+Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
+
+You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs][docs.using-qovery.configuration.clusters#logs]
+
+</li>
+</ol>
+</Steps>
+
+
+### Managing your Cluster Settings
+
+To manage the settings of an existing cluster:
+
+<Steps headingDepth={3}>
+<ol>
+<li>
+
+Open your [Qovery Console][urls.qovery_console].
+
+</li>
+<li>
+
+On the left menu bar, click on the Cluster page.
+
+</li>
+<li>
+
+To access your cluster settings, click on the wheel button:
+
+<p align="center">
+  <img src="/img/configuration/clusters/cluster_settings.png" alt="Display Cluster Settings" />
+</p>
+
+</li>
+
+</ol>
+</Steps>
+
+Below you can find a description of each section
+
+#### General
+
+The `General` tab allows you to define high-level information on your cluster:
+
+|Item|Description|
+|--------------|---------------------------|
+|Cluster Name|To edit the name of your cluster.|
+|Description|To enter or edit the description of your cluster.|
+|Production Cluster|To enter or edit the production flag of your cluster.|
+
+#### Credentials
+
+Here you can manage here the cloud provider credentials associated with your cluster.
+
+If you need to change the credentials:
+- generate a new set of credentials on your cloud provider([Procedure for Scaleway account][docs.getting-started.install-qovery.scaleway.cluster-managed-by-qovery.quickstart#attach-scaleway-credentials])
+- create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
+
+Once created and associated, you need to [updating your cluster][docs.using-qovery.configuration.clusters#updating-a-cluster] to apply the change.
+
+#### Image registry
+
+In this tab, you will see that a container registry already exist (called `registry-{$UIID}`). 
+This is your cloud provider container registry used by Qovery to manage the deployment of your applications by mirroring the docker images.
+
+The credentials configured on this registry are the one used to create the cluster. But you can still update them if you prefer to manage them separately (dedicated pair of creds just to access the registry).
+
+Check [this link][docs.using-qovery.deployment.image-mirroring] for more information.
\ No newline at end of file
diff --git a/website/docs/using-qovery/maintenance.md b/website/docs/using-qovery/maintenance.md
index 0b55f70de2..10e8af2ed2 100644
--- a/website/docs/using-qovery/maintenance.md
+++ b/website/docs/using-qovery/maintenance.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2022-11-11"
+last_modified_on: "2024-11-21"
 title: Maintenance
 description: "Maintainance and operation for your Qovery cluster and applications"
 sidebar_label: hidden
@@ -94,7 +94,7 @@ You can update or rotate manually credentials on your AWS account this way:
 
 1. Click on the `Create access key` button
 2. Save the `access key` and `secret access Key` in a safe place
-3. Go to your Qovery dashboard to [update the credentials on Qovery console][docs.using-qovery.configuration.clusters#credentials].
+3. Go to your Qovery dashboard to [update the credentials on Qovery console][docs.using-qovery.configuration.clusters.aws#credentials].
 4. `Deploy` the cluster once again to apply changes
 5. Once the cluster is fully updated, wait 2h (to ensure all ongoing deployments are done)
 6. Delete the old access key from the AWS console:
@@ -216,4 +216,4 @@ You will see the following output:
 ```
 
 
-[docs.using-qovery.configuration.clusters#credentials]: /docs/using-qovery/configuration/clusters/#credentials
+[docs.using-qovery.configuration.clusters.aws#credentials]: /docs/using-qovery/configuration/clusters/aws/#credentials
diff --git a/website/docs/using-qovery/maintenance.md.erb b/website/docs/using-qovery/maintenance.md.erb
index 1d0a467fbc..220832af0e 100644
--- a/website/docs/using-qovery/maintenance.md.erb
+++ b/website/docs/using-qovery/maintenance.md.erb
@@ -83,7 +83,7 @@ You can update or rotate manually credentials on your AWS account this way:
 
 1. Click on the `Create access key` button
 2. Save the `access key` and `secret access Key` in a safe place
-3. Go to your Qovery dashboard to [update the credentials on Qovery console][docs.using-qovery.configuration.clusters#credentials].
+3. Go to your Qovery dashboard to [update the credentials on Qovery console][docs.using-qovery.configuration.clusters.aws#credentials].
 4. `Deploy` the cluster once again to apply changes
 5. Once the cluster is fully updated, wait 2h (to ensure all ongoing deployments are done)
 6. Delete the old access key from the AWS console:
diff --git a/website/docs/using-qovery/troubleshoot/service-deployment-troubleshoot.md b/website/docs/using-qovery/troubleshoot/service-deployment-troubleshoot.md
index db9591f44a..b732991046 100644
--- a/website/docs/using-qovery/troubleshoot/service-deployment-troubleshoot.md
+++ b/website/docs/using-qovery/troubleshoot/service-deployment-troubleshoot.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2024-11-04"
+last_modified_on: "2024-11-26"
 title: Service Deployment Troubleshoot
 description: "How to troubleshoot your service deployments with Qovery"
 hide_pagination: true
@@ -67,9 +67,9 @@ Here are the possible solutions you can apply:
 
 * Reduce the resources (CPU/RAM) allocated to your existing/new service. Have a review of the deployed services and see if you can save up some resources by reducing their CPU/RAM setting. Remember to re-deploy the applications when you edit the resource. Have a look at [the resource section for more information][docs.using-qovery.configuration.application#resources].
 
-* Select a bigger instance type for your cluster (in terms of CPU/RAM). By increasing it, it will unlock the deployment of your application (since new resources have been added). Check your [cluster settings][docs.using-qovery.configuration.clusters#managing-your-cluster-settings], and change the instance type of your cluster.
+* Select a bigger instance type for your cluster (in terms of CPU/RAM). By increasing it, it will unlock the deployment of your application (since new resources have been added). Check your cluster settings, and change the instance type of your cluster.
 
-* (only for Managed kubernets clusters) Increase the maximum number of nodes of your cluster. By increasing it, it will allow the cluster autoscaler to add a new node and allow the deployment of your application (since new resources have been added). Check your [cluster settings][docs.using-qovery.configuration.clusters#managing-your-cluster-settings], and increase the maximum number of nodes of your cluster.
+* Increase the maximum number of nodes of your cluster. By increasing it, it will allow the cluster autoscaler to add a new node and allow the deployment of your application (since new resources have been added). Check your cluster settings, and increase the maximum number of nodes of your cluster. Note: If you are using a self-managed cluster, this operation cannot be performed through the Qovery console.
 
 <Alert type="info">
 
@@ -264,7 +264,6 @@ Open a ticket to the Cloud Provider support, and as to raise this limit.
 [docs.using-qovery.configuration.application#ports]: /docs/using-qovery/configuration/application/#ports
 [docs.using-qovery.configuration.application#resources]: /docs/using-qovery/configuration/application/#resources
 [docs.using-qovery.configuration.application-health-checks#initial-delay-in-seconds]: /docs/using-qovery/configuration/application-health-checks/#initial-delay-in-seconds
-[docs.using-qovery.configuration.clusters#managing-your-cluster-settings]: /docs/using-qovery/configuration/clusters/#managing-your-cluster-settings
 [docs.using-qovery.configuration.clusters#what-are-the-different-instance-types-available-when-creating-a-cluster]: /docs/using-qovery/configuration/clusters/#what-are-the-different-instance-types-available-when-creating-a-cluster
 [docs.using-qovery.configuration.lifecycle-job#triggers]: /docs/using-qovery/configuration/lifecycle-job/#triggers
 [docs.using-qovery.interface.cli#shell]: /docs/using-qovery/interface/cli/#shell
diff --git a/website/docs/using-qovery/troubleshoot/service-deployment-troubleshoot.md.erb b/website/docs/using-qovery/troubleshoot/service-deployment-troubleshoot.md.erb
index 57f9b35ebf..b05cbccfc2 100644
--- a/website/docs/using-qovery/troubleshoot/service-deployment-troubleshoot.md.erb
+++ b/website/docs/using-qovery/troubleshoot/service-deployment-troubleshoot.md.erb
@@ -55,9 +55,9 @@ Here are the possible solutions you can apply:
 
 * Reduce the resources (CPU/RAM) allocated to your existing/new service. Have a review of the deployed services and see if you can save up some resources by reducing their CPU/RAM setting. Remember to re-deploy the applications when you edit the resource. Have a look at [the resource section for more information][docs.using-qovery.configuration.application#resources].
 
-* Select a bigger instance type for your cluster (in terms of CPU/RAM). By increasing it, it will unlock the deployment of your application (since new resources have been added). Check your [cluster settings][docs.using-qovery.configuration.clusters#managing-your-cluster-settings], and change the instance type of your cluster.
+* Select a bigger instance type for your cluster (in terms of CPU/RAM). By increasing it, it will unlock the deployment of your application (since new resources have been added). Check your cluster settings, and change the instance type of your cluster.
 
-* (only for Managed kubernets clusters) Increase the maximum number of nodes of your cluster. By increasing it, it will allow the cluster autoscaler to add a new node and allow the deployment of your application (since new resources have been added). Check your [cluster settings][docs.using-qovery.configuration.clusters#managing-your-cluster-settings], and increase the maximum number of nodes of your cluster.
+* Increase the maximum number of nodes of your cluster. By increasing it, it will allow the cluster autoscaler to add a new node and allow the deployment of your application (since new resources have been added). Check your cluster settings, and increase the maximum number of nodes of your cluster. Note: If you are using a self-managed cluster, this operation cannot be performed through the Qovery console.
 
 <Alert type="info">
 
diff --git a/website/guides/installation-guide/guide-amazon-web-services.md b/website/guides/installation-guide/guide-amazon-web-services.md
index 7f4b88ab0f..998f86eb21 100644
--- a/website/guides/installation-guide/guide-amazon-web-services.md
+++ b/website/guides/installation-guide/guide-amazon-web-services.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2024-01-02"
+last_modified_on: "2024-11-21"
 $schema: "/.meta/.schemas/guides.json"
 title: Install Qovery on your Amazon Web Services account
 description: Learn how to install Qovery on your Amazon Web Services (AWS) account
diff --git a/website/sidebars.js b/website/sidebars.js
index 559d97e2d2..710a22d794 100644
--- a/website/sidebars.js
+++ b/website/sidebars.js
@@ -188,7 +188,17 @@ module.exports = {
                 "using-qovery/configuration/organization/labels-annotations",
               ],
             },
-            "using-qovery/configuration/clusters",
+            {
+              type: 'category',
+              label: 'Clusters',
+              items: [
+                "using-qovery/configuration/clusters",
+                "using-qovery/configuration/clusters/aws",
+                "using-qovery/configuration/clusters/aws-with-karpenter",
+                "using-qovery/configuration/clusters/gcp",
+                "using-qovery/configuration/clusters/scaleway",
+              ],
+            },
             "using-qovery/configuration/cluster-advanced-settings",
             "using-qovery/configuration/project",
             "using-qovery/configuration/environment",
diff --git a/website/sidebars.js.erb b/website/sidebars.js.erb
index 511b5a6e1f..275919f8e2 100644
--- a/website/sidebars.js.erb
+++ b/website/sidebars.js.erb
@@ -188,7 +188,17 @@ module.exports = {
                 <%= metadata.links.fetch_id("docs.using-qovery.configuration.organization.labels-annotations").to_json %>,
               ],
             },
-            <%= metadata.links.fetch_id("docs.using-qovery.configuration.clusters").to_json %>,
+            {
+              type: 'category',
+              label: 'Clusters',
+              items: [
+                <%= metadata.links.fetch_id("docs.using-qovery.configuration.clusters").to_json %>,
+                <%= metadata.links.fetch_id("docs.using-qovery.configuration.clusters.aws").to_json %>,
+                <%= metadata.links.fetch_id("docs.using-qovery.configuration.clusters.aws-with-karpenter").to_json %>,
+                <%= metadata.links.fetch_id("docs.using-qovery.configuration.clusters.gcp").to_json %>,
+                <%= metadata.links.fetch_id("docs.using-qovery.configuration.clusters.scaleway").to_json %>,
+              ],
+            },
             <%= metadata.links.fetch_id("docs.using-qovery.configuration.cluster-advanced-settings").to_json %>,
             <%= metadata.links.fetch_id("docs.using-qovery.configuration.project").to_json %>,
             <%= metadata.links.fetch_id("docs.using-qovery.configuration.environment").to_json %>,
diff --git a/website/static/img/configuration/clusters/cluster_hosting_selection.png b/website/static/img/configuration/clusters/cluster_hosting_selection.png
new file mode 100644
index 0000000000..6b89225f5f
Binary files /dev/null and b/website/static/img/configuration/clusters/cluster_hosting_selection.png differ
diff --git a/website/static/img/configuration/clusters/cluster_hosting_selection.png:Zone.Identifier b/website/static/img/configuration/clusters/cluster_hosting_selection.png:Zone.Identifier
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/website/static/img/configuration/clusters/cluster_hosting_selection_aws.png b/website/static/img/configuration/clusters/cluster_hosting_selection_aws.png
new file mode 100644
index 0000000000..a5996eee6b
Binary files /dev/null and b/website/static/img/configuration/clusters/cluster_hosting_selection_aws.png differ
diff --git a/website/static/img/configuration/clusters/cluster_hosting_selection_gcp.png b/website/static/img/configuration/clusters/cluster_hosting_selection_gcp.png
new file mode 100644
index 0000000000..25652a7500
Binary files /dev/null and b/website/static/img/configuration/clusters/cluster_hosting_selection_gcp.png differ
diff --git a/website/static/img/configuration/clusters/cluster_hosting_selection_scw.png b/website/static/img/configuration/clusters/cluster_hosting_selection_scw.png
new file mode 100644
index 0000000000..52263caf83
Binary files /dev/null and b/website/static/img/configuration/clusters/cluster_hosting_selection_scw.png differ
diff --git a/website/static/img/configuration/clusters/cluster_section_access.png b/website/static/img/configuration/clusters/cluster_section_access.png
index c8cec1d4ad..d4343b3ba0 100644
Binary files a/website/static/img/configuration/clusters/cluster_section_access.png and b/website/static/img/configuration/clusters/cluster_section_access.png differ
diff --git a/website/static/img/configuration/clusters/cluster_section_access.png:Zone.Identifier b/website/static/img/configuration/clusters/cluster_section_access.png:Zone.Identifier
new file mode 100644
index 0000000000..e69de29bb2