Jump toSuggest an edit

Setting up Traefik v2 and cert-manager on Kapsule

Reviewed on 24 April 2024Published on 01 July 2020
  • k8s
  • Kapsule
  • Traefik
  • cert-manager
  • Load-Balancer

Traefik (pronounced traffic) is a modern HTTP reverse proxy and Load Balancer designed to make the deployment of microservices easy. Traefik integrates with any HTTP and TCP-based applications and every major cluster technology.

Our goal in this tutorial is to:

  • Expose Traefik 2 using a Scaleway Load Balancer
  • Deploy a test application on our cluster
  • Expose this test application through an ingress object, using Traefik 2 (deployed by Kapsule)
  • Expose this application securely (with https and Let’s Encrypt, using cert-manager)

This tutorial is divided into two parts:

  • First, we will check how to expose the Traefik 2 ingress controller shipped with Kapsule with a Scaleway LoadBalancer.
  • In the second part, we will deploy a test application to expose it in HTTP with a DNS managed by Scaleway DNS, then use cert-manager to create a Let’s Encrypt certificate and expose this application securely in https.

Before you start

To complete the actions presented below, you must have:

  • A Scaleway account logged into the console
  • Owner status or IAM permissions allowing you to perform actions in the intended Organization
  • A Kubernetes Kapsule cluster with an ingress controller (Traefik 2)
  • Downloaded the corresponding kubeconfig file and ensured the kubectl is configured and working

Deploying a Load Balancer using the Easy Deploy feature


You need a Kubernetes Kapsule cluster deployed with Traefik 2 to follow this tutorial. To deploy your cluster with Traefik 2, use the Easy Deploy feature.

  1. Click Kubernetes in the Containers section of the Scaleway console side menu. The Kubernetes dashboard displays.
  2. Click the name of your cluster. The cluster overview page displays.
  3. Click the Easy Deploy tab on your clusters overview page. The Easy Deploy feature displays.
  4. Click Deploy an Application. The application deployment wizard displays.
  5. Select Application Library, type Traefik in the search bar and select the Traefik 2 Ingress application.
  6. Enter the name traefik for the application and type the kube-system namespace name.
  7. Click Deploy an application to deploy the Load Balancer on your cluster.

Creating a wildcard DNS record and pointing your domain name to the IP address

We will be using the new Domains and DNS product, available on Scaleway, to create a wildcard record pointing to this IP address (the domain used in this tutorial will be “”). A wildcard record (* allows you to point any subdomain of your domain to the configured IP address.


Traefik listens by default on ports 80 and 443 of the public IP of any node of your cluster. You can retrieve the external IP of your clusters’ nodes by running the kubectl get node -o wide command.

Verify that the domain is pointed to the IP address of your LoadBalancer:

host has address

Your domain is now pointing to your LoadBalancer IP, you can resolve any of your subdomains with that IP.

Deploying a test application

In this step, we deploy a test application called “tea coffee” which is only printing tea or coffee depending on the subpath you will reach.

  1. Use kubectl to create the application
    kubectl create -f
  2. Create an associated ingress object pointing to by creating and editing the file ingress-teacoffee.yml in your favorite text editor:
    kind: Ingress
    name: cafe-ingress
    - host:
    - path: /tea
    pathType: Prefix
    name: tea-svc
    number: 80
    - path: /coffee
    pathType: Prefix
    name: coffee-svc
    number: 80
  3. Run the following command to set up the configuration:
    kubectl create -f ingress-teacoffee.yml created
  4. You can now use curl to send an HTTP request to this URL. Traefik 2 is working correctly with your wildcard DNS in plain, unencrypted HTTP (web unsecure).
    Server address:
    Server name: tea-69c99ff568-c2lc2
    Date: 29/Jun/2020:13:01:19 +0000
    URI: /tea
    Request ID: f3b7f1bcd5dd841d420236906146af9f
  5. To proceed with the tutorial, delete the ingress object created. It will be replaced in future steps.
    kubectl delete ing cafe-ingress

Creating the Let’s Encrypt issuer

Cert-manager is in charge of creating Let’s Encrypt TLS certificates to make your website secure, to sum up:

  • Create an ingress object for a specific subdomain (for instance
  • Let’s Encrypt must be sure that the domain belongs to you. For this reason, Let’s Encrypt requests a “challenge”, in our case, an HTTP challenge. This means that Let’s Encrypt will try to reach, and can see a specific hash on this page.
  • Cert-manager is serving this page for you by creating an ingress object and using an HTTP server.
  • When the challenge is ok, the certificate is created and added to a certificate object.
  • You can then use this certificate object to serve your website securely (HTTPS).

Since Cert Manager is already deployed on your cluster, you can directly proceed to create Let’s Encrypt certificates for securing your applications.

  1. Create a cluster issuer that allows you to specify:

    • the Let’s Encrypt server, if you want to replace the production environment with the staging one.
    • the mail used by Let’s Encrypt to warn you about certificate expiration.

    Copy and paste the following configuration in the file cluster-issuer.yaml using your favorite text editor:

    kind: ClusterIssuer
    name: letsencrypt-prod
    # You must replace this email address with your own.
    # Let's Encrypt will use this to contact you about expiring
    # certificates, and issues related to your account.
    # Secret resource used to store the account's private key.
    name: issuer-account-key
    # Add a single challenge solver, HTTP01
    - http01:
    class: traefik
  2. Use kubectl to apply the configuration:

    kubectl create -f cluster-issuer.yaml created

Creating and using a Let’s Encrypt certificate to serve your website in HTTPS

In this step, you will create the Let’s Encrypt certificate by specifying:

  • The secret name where the certificate will be stored.
  • The subdomain for which you want to create a certificate.
  • The issuer created before (letsencrypt-prod).
  1. Create and edit a file mycert.yaml as follows:

    kind: Certificate
    name: teacoffee-cert
    namespace: default
    secretName: teacoffee-cert
    name: letsencrypt-prod
    kind: ClusterIssuer
  2. Apply the configuration using kubectl:

    kubectl create -f mycert.yaml created
  3. Check the certificate has been correctly created (you should see “Ready” in the condition):

    kubectl describe certificate -n default teacoffee-cert
    Common Name:
    Dns Names:
    Issuer Ref:
    Kind: ClusterIssuer
    Name: letsencrypt-prod
    Secret Name: teacoffee-cert
    Last Transition Time: 2021-02-24T16:50:42Z
    Message: Certificate is up to date and has not expired
    Reason: Ready
    Status: True
    Type: Ready
    Not After: 2021-05-25T15:50:41Z
    Not Before: 2021-02-24T15:50:41Z
    Renewal Time: 2021-04-25T15:50:41Z
    Revision: 1
    Type Reason Age From Message
    ---- ------ ---- ---- -------
    Normal Requested 11m cert-manager Created new CertificateRequest resource "teacoffee-cert-4271191437"
    Normal Issued 48s cert-manager Certificate issued successfully
  4. Create a Standard Ingress, with TLS enabled (with the name of the secret created by the creation of the certificate, in our case: teacoffee-cert). To do so create file mysite.yaml, copy the following content into it, and run kubectl with the following command: kubectl create -f mysite.yaml.

    kind: Ingress
    name: testcoffee
    namespace: default
    annotations: websecure
    - secretName: teacoffee-cert
    - host:
    - path: /tea
    pathType: Prefix
    name: tea-svc
    number: 80
    - path: /coffee
    pathType: Prefix
    name: coffee-svc
    number: 80
  5. Check that your website is accessible via HTTPS:

    curl -v
    * Trying
    * TCP_NODELAY set
    * Connected to ( port 443 (#0)
    * successfully set certificate verify locations:
    * CAfile: /etc/ssl/certs/ca-certificates.crt
    CApath: /etc/ssl/certs
    * Server certificate:
    * subject:
    * start date: Jun 29 12:46:04 2020 GMT
    * expire date: Sep 27 12:46:04 2020 GMT
    * subjectAltName: host "" matched cert's ""
    * issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
    * SSL certificate verify ok.
    > GET /tea HTTP/2
    > Host:
    > User-Agent: curl/7.58.0
    > Accept: */*
    Server address:
    Server name: tea-69c99ff568-c2lc2
    Date: 29/Jun/2020:13:52:42 +0000
    URI: /tea
    Request ID: b7a45b7b20bd712df75f8ce8596db50d
    * Connection #0 to host left intact
  6. Access the Traefik 2 dashboard by using this command:

    kubectl port-forward -n kube-system $(kubectl get pods -n kube-system --selector "" --output=name | head -n 1) 9000:9000
  7. You can then access the Traefik 2 dashboard with this address: (Note the trailing /.)

To go further, you might be interested in the following pages:

  • Letsencrypt
  • Traefik 2
  • cert-manager
Docs APIScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCarreer
© 2023-2024 – Scaleway