À propos d’OKS

Cette page est à ce jour disponible en anglais uniquement.

OUTSCALE Kubernetes as a Service (OKS) is a managed Kubernetes service designed for efficiency and ease of use.

Unlike conventional cluster deployments requiring extensive manual configuration and upkeep, OKS provisions Kubernetes clusters with predefined settings and pre-installed essential services. This simplifies your workflow by automatically managing updates of Kubernetes versions and security patches, allowing you to focus on the deployment of your containerized applications.

To use OKS, you need to send a request to our Support team at support@outscale.com.

Kubernetes Versions Support

OKS supports the following recent versions of Kubernetes:

Table 1. Kubernetes Supported Versions
Kubernetes Version	Link
1.31	Version announcement
1.30	Version announcement
1.29	Version announcement

Clusters

An OKS cluster is a Kubernetes cluster that is automatically deployed based on a configuration that you specify. It consists of a control plane, which manages the cluster, and worker nodes, which run your containerized applications.

OKS allows you to create and manage clusters using simple API calls, without the complexity of a manual setup. To facilitate this, we provide a dedicated command-line tool. For more information, see Installer et configurer OKS CLI.

3DS OUTSCALE cannot guarantee the reliability of OKS clusters that are configured manually.

Projects

In OKS, clusters are organized into different projects. A project is a top-level container that serves as a logical grouping of clusters and other related resources.

Projects enables you to:

Organize and isolate your Cloud resources, to prevent issues in one project from affecting other projects
Better track your costs, by using separate billing accounts and cost management

A project involves the reservation of a specific CIDR block for networking.

For more information, see Gérer vos projets avec OKS CLI.

Control Planes

A control plane is the management layer of the Kubernetes cluster: it manages and coordinates the other resources by making decisions about scheduling applications, monitoring the system’s health, and scaling.

With OKS, the control plane is fully managed, meaning you do not need to maintain or update it yourself.

OKS provides different control plane types you can choose from. Control plane types define the hardware characteristics of the control plane, such as the number and performance of the control plane nodes.

When creating an OKS cluster, you must thus specify a control plane type among the following:

Table 2. Control Planes Types
Name	Description	Can upgrade?	High availability (HA)	Recommended maximal size of cluster**
`cp.mono.master`*	Single dedicated master, with 4 GiB RAM*	No*	No*	Up to 10 nodes*
`cp.3.masters.small`	3 dedicated masters, with 4 GiB RAM each	Yes	Yes	Up to 50 nodes
`cp.3.masters.medium`	3 dedicated masters, with 8 GiB RAM each	Yes	Yes	Up to 200 nodes
`cp.3.masters.large`	3 dedicated masters, with 16 GiB RAM each	Yes	Yes	Up to 400 nodes

* cp.mono.master is only recommended for testing purposes or ephemeral clusters, as it has no HA options, no SLA applicable, and is not suited to long-term or production use. It also cannot be upgraded to another sizing, so to change it to a multi-master control plane it has to be recreated.

** The recommended maximum cluster size is based on low-load environments. High-load production clusters may require a larger control plane.

Choosing a control plane type does not affect the availability of cluster management tools.

Worker Nodes

In a cluster, worker nodes (also referred to as the data plane) are the virtual machines (VMs) responsible for running your application. Worker nodes do not host control plane components, so they can be added or removed at any time without disrupting the cluster’s availability.

Worker nodes in OKS clusters are neither visible nor directly accessible in your OUTSCALE account. This design is intentional, in order to follow the "Treat your Kubernetes clusters as cattle, not pets" best practice.

Node Pools

A node pool is a group of worker nodes within an OKS cluster, managed by the control plane. Node pools consist of nodes of the same type and within the same Region, though they may be distributed across multiple Subregions. Clusters can have multiple node pools at the same time.

In OKS, worker nodes are always organized into node pools, meaning "worker nodepool" can be used as a synonym for a defined set of worker nodes.

Related Pages