Scaleway Elements Kubernetes Kapsule provides a managed environment to create, configure and run a cluster of preconfigured machines for containerized applications. You will be able to create Kubernetes clusters without the complexity to manage the infrastructure.
The service offers full flexibility such as:
To administrate your Kubernetes Cluster easily, Scaleway provides a
.kubeconfig file that allows to manage your cluster from your local computer by using
kubectl. Kubectl is the command line interface for running commands against Kubernetes clusters.
To learn more about Scaleway Elements Kubernetes Kapsule, refer to the FAQ.
- You have an account and are logged into console.scaleway.com
Kubernetes is an extensible open-source platform, built to manage containerized workloads and services. For more detailed information, refer to our Introduction into Kubernetes and the official documentation.
A cluster is a set of machines, called nodes, running containerized applications managed by Kubernetes. The Kubernetes Control Plane and associated load balancers are managed by Scaleway. A cluster has several worker nodes and at least one control plane. Each cluster is built for High Availability with a redundancy on the Control Plane.
Consider the following when creating a Control Plane:
The Pool resource is a group of Scaleway compute instances, organized by type (e.g., GP1-S, GP1-M).
It represents the computing power of the cluster and contains the Kubernetes nodes, on which the containers run.
Consider the following when creating a Pool:
Load balancing refers to efficiently distributing incoming network traffic across a group of backend servers. Scaleway services manage the traffic between the API masters. As a user, the load balancer is a service entirely managed by Scaleway.
Namespaces are used in Kubernetes to divide cluster resources between multiple users. For detailed information, refer to Kubernetes official documentation on Namespaces
An API object that manages external access to the services in a cluster, typically HTTPS. Ingress can provide load balancing, SSL termination and name-based virtual hosting.
1 . Sign in to your Scaleway account
2 . Click Kapsule on the side menu. The Kapsule page is displayed.
3 . Click Create a cluster
4 . On the Create a Cluster page, enter:
5 . Click Create Cluster
Your cluster is being deployed
Once your cluster is created, it appears in the Clusters List.
Several options are available from the pop-up menu on the cluster list page:
.kubeconfigfile of the Cluster
To view your cluster information, click on the cluster itself. The cluster overview page provides several information:
If you click on the Pools tab, you are able to add, edit or delete a pool on your cluster.
If you click on the Nodes tab, you are able to reboot or replace nodes on your cluster.
Once the cluster is created, a
.kubeconfig file is available for download to manage several Kubernetes clusters.
1 . Download the
.kubeconfig files from the Clusters Details page:
2 . Set a variable for the
.kubeconfig file. You have two options to do so:
# export KUBECONFIG=/$HOME/Downloads/myconfig # kubectl get nodes
# mv $HOME/Downloads/myconfig $HOME/.kube/config # kubectl get nodes
3 . Configure the
bash # Use provided .kubeconfig file to access scw Kubernetes cluster kubectl config --kubeconfig path/to/.kubeconfig/file set-context ...
1 . Download the
.kubeconfig file of your cluster from the console:
2 . Access the dashboard through kubectl proxy
3 . Open a browser and paste the following URL (for Kubernetes v1.16):
For Kubernetes prior to version 1.16 use the following URL:
4 . Select Kubeconfig as authentication method, choose the kubeconfig file to use and validate
Important: The Kubernetes dashboard is only available if the dashboard option is selected.
An Ingress Controller is an entry point that ingests your HTTP/HTTPS traffic and dispatches it to your services. More closely, it is a reverse proxy that will dynamically configure itself and will forward HTTP/HTTPS traffic to your services.
It is possible to configure an Ingress Controller during cluster creation. Click on Advanced Options and click on Yes to enable the Ingress Controller. It is possible to setup
kubectl get nodes -o wide
Kapsule presents the following limitations:
/etcfolder on Kubernetes Kapsule nodes might be used for internal cluster actions. Prefer
/datafor local storage, even though local storage is not recommended in stateless Kubernetes clusters.
To keep practicing with Kubernetes Kapsule, refer to
To learn more about Scaleway Elements Kubernetes Kapsule, refer to