---
title: How to deploy containerized applications with the Easy Deploy feature
description: Learn how to deploy containerized applications with the Easy Deploy feature on Scaleway Kubernetes clusters.
tags: deploy containerized-applications easy-deploy
dates:
  validation: 2025-07-01
  posted: 2020-10-14
---
import Requirements from '@macros/iam/requirements.mdx'

import image from './assets/scaleway-kubernetes-application-library.webp'
import image2 from './assets/scaleway-kubernetes-yaml-edit.webp'
import image3 from './assets/scaleway-kubernetes-kubectl-all.webp'
import image4 from './assets/scaleway-kubernetes-wordpress.webp'
import image5 from './assets/scaleway-update-container.webp'
import image6 from './assets/scaleway-kubernetes-edit-application.webp'


The Easy Deploy feature allows you to pull images directly from [Scaleway Container Registry](/container-registry/concepts/#container-registry), instantly deploying containerized applications in your [Kubernetes Kapsule](/kubernetes/concepts/#kubernetes-kapsule) and [Kubernetes Kosmos](/kubernetes/concepts/#kubernetes-kosmos) clusters.

You can also deploy off-the-shelf applications pre-configured for Scaleway products, such as Load Balancer and Block Storage.

**With only the basic options to set, you can use Kubernetes Kapsule or Kosmos without needing to manage your `.yaml` manifests.**

<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- A valid [API key](/iam/how-to/create-api-keys/)
- Created a Scaleway Kubernetes [Kapsule](/kubernetes/how-to/create-cluster/) or [Kosmos](/kubernetes/how-to/create-kosmos-cluster/) cluster
- [Created a Scaleway Container Registry namespace](/container-registry/how-to/create-namespace/) (not mandatory if deploying using the Application Library)

## How to deploy an application

### Deployment from Scaleway Container Registry

<Message type="note">
  To deploy a container from an image stored within Container Registry, you must be logged in to the [Scaleway console](https://console.scaleway.com/).
</Message>

1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Kubernetes Kapsule dashboard displays.
2. From the drop-down menu, select the geographical region you want to manage.
3. Click the name of the cluster you wish to deploy your image on. The **Cluster information** tab displays.
4. Click the **Easy Deploy** tab.
5. Click **Deploy application**.
6. Deploy the application. This step can be done in two ways:
  * **Deployment from Container Registry**

    * After selecting **Container Registry**, enter a name for your application as well as the Kubernetes namespace on which the deployment will run. By default, the application is deployed on the `default` namespace.

    * Select the Container Registry namespace you would like to deploy from the Container Registry. Specify **Container** and **Tag**.

      <Message type="note">
      Your container needs to be public in order to be selected and deployed.
      </Message>

      You can configure the deployment of your clusters in two ways: **Deployments** or **CronJobs**.

      A **Deployment** represents a set of identical Pods with no individual identities managed by a deployment controller. The deployment controller runs multiple replicas of an application as specified in a ReplicaSet. If any Pods fail or become unresponsive, the deployment controller replaces them until the actual state equals the desired state. **When using a deployment Kubernetes object, you do not need to manage your Pods or ReplicaSet**.

      You can set up a Load Balancer for your container, create several replicas and add environment variables, such as database host/credentials.

      **CronJobs** in Kubernetes work like traditional cron jobs on Linux. They can be used to run tasks at a specific time or interval and may be useful for jobs such as backups or cleanup tasks. You can edit your deployments and CronJob settings, but cannot modify the type of deployment nor the container to deploy. If you need to do so, you will need to delete the existing deployment and create a new one accordingly.

      For CronJobs, an instruction schedule must be defined. Each cron instruction is scheduled using the following syntax:
      ```
      Minute (mm): 0 - 59
      Hour (hh): 0 - 23
      Day of the Month (dd): 1 - 31
      Month (MMM): 1 - 12
      Day of the Week (DDD): 0 - 6 (Sunday to Saturday, 7 is also Sunday on some systems)
      ```
      Each instruction can also be:
      ```
      *: at each unit (1, 2, 3, 4...)
      5,8: at unit 5 and 8
      2-5: at unit 2 to 5
      */3: every 3 unit (0, 3, 6, 9...)
      10-20/3: every 3 units, between the tenth and the twentieth (10, 13, 16, 19)

      Example: 45 23 * * 6
      This example executes program at 23:45 (11:45 PM) every Saturday.
      ```
      You must also include a path to your script in the **Command** box and set up environment variables.

    * Select a deployment type and fill out the prompted information according to your choice. A summary of your choices is available.

    *  Click **Deploy application** to proceed. The list of your deployed applications displays.


### Deployment from Application Library

<Message type="important">
  Depending on the application and the configuration you choose, additional charges may apply. These can include, but are not limited to:

  - Block Storage (e.g., persistent volumes)
  - Load Balancers (for managing traffic across applications)
  - Logging services (e.g., Promtail to Cockpit log forwarding billed as [external data source](/cockpit/how-to/create-external-data-sources/))
  - Other application-specific resources that generate costs

  We recommend reviewing the documentation for each application and checking your resource usage regularly, using the [Cost Manager in the console](https://console.scaleway.com/billing/consumption) to understand any associated costs.
</Message>

    * After selecting **Application Library**, enter a name for your container as well as the Kubernetes namespace on which the deployment will run. By default, the application is deployed on the `default` namespace.

    <Lightbox image={image} alt="" />

    * Search and select the application you want to deploy from our library. For example, you can choose to deploy the WordPress application. A default `yaml` configuration will preload to show the specifics defaults values of the application. You can modify or add values to the `yaml` as you see fit.

      <Lightbox image={image2} alt="" />

      * Using `scw-bssd` Storage type will imply the creation of Scaleway Block Storage resources by your Kubernetes cluster, having an impact on your final invoice.
      * Using `LoadBalancer` service will imply the creation of a Scaleway Load Balancer, having an impact on your final invoice.

    * Click **Deploy application** to proceed. The list of your deployed applications displays.

    * If you created a LoadBalancer to expose your application, use the `kubectl` command to list the services of your cluster and get the LoadBalancer external IP.

      <Lightbox image={image3} alt="" />

    * Get the Load Balancer's external IP and use it in your web browser to access your application (WordPress in this case)
      <Lightbox image={image4} alt="" />

    <Message type="tip">
      We provide dedicated tutorials for deployment of the most popular applications using Easy Deploy:
      * [Deploy Argo CD on Scaleway Kubernetes clusters using Easy Deploy](/tutorials/easydeploy-argocd/)
      * [Deploy Vault on Scaleway Kubernetes clusters using Easy Deploy](/tutorials/easydeploy-vault/)
      * [Deploy Grafana on Scaleway Kubernetes clusters using Easy Deploy](/tutorials/easydeploy-grafana/)
      * [Deploy GitLab Server on Scaleway Kubernetes clusters using Easy Deploy](/tutorials/easydeploy-gitlab-server/)
      * [Deploy GitLab Runner on Scaleway Kubernetes clusters using Easy Deploy](/tutorials/easydeploy-gitlab-runner/)
    </Message>

## How to edit an application

1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Kubernetes Kapsule overview displays.
2. From the drop-down menu, select the geographical region you want to manage.
3. Click <Icon name="edit" /> next to the container you wish to edit, then click **Edit** in the menu. A pop-up displays with the configuration options.
4. When modifying an application deployed from **Container Registry**, modify the container parameters according to your requirements, then click **Update container** to conclude.
    <Lightbox image={image5} alt="" />
    <Message type="note">
      It is not possible to modify a container **type**. If you wish to use a different type, you must create a new container.
    </Message>
5. When modifying an application deployed from the **Application Library**, modify the application configuration according to your requirements, then click **Update and deploy** to conclude.
    <Lightbox image={image6} alt="" />

## How to delete an application

1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Kubernetes Kapsule dashboard displays.
2. From the drop-down menu, select the geographical region you want to manage.
3. Click <Icon name="edit" /> next to the container you want to delete, then click **Delete** in the pop-up menu. A message prompt displays to request confirmation.
4. To confirm the deletion of the deployment, click **Delete Deployment**.
    <Message type="important">
      Deleting a deployment is irreversible, and all data related to the deployment will be deleted.
    </Message>