Simplify the management of Clever Cloud services via Kubernetes with our new operator

2025 04 15 clever cloud banniere blog clever kubernetes operator en
For the past two years, we've been enabling our customers to combine the ease of deployment of Clever Cloud with an existing Kubernetes infrastructure through an operator.

Over the last few months, we’ve been working on making it easier to learn and more complete, supporting our new services. This has led to the release of version 0.7.0. Here’s an overview of the main new features.

New name, simplified authentication

First of all, it’s getting a new name. The repository has been changed from clever-operator to clever-kubernetes-operator. This reflects better the nature and purpose of the project, highlighting its central role in the integration of Kubernetes with Clever Cloud.

We also listened to a number of users’ requests for simpler authentication management. Whereas you previously had to integrate it into a complete OAuth process, now you can simply generate and use an API Token. The Kubernetes operator can also retrieve the credentials of the user connected to Clever Tools, enabling you to use it after executing a clever login.

Adding our new services

With this update, we’re adding the many products we’ve launched in recent months, which can now be operator-driven to enrich the capabilities of your Kubernetes cluster :

Updating existing products

We also reviewed the supported versions of existing products, in particular our databases. For example, we’ve added PostgreSQL versions 16 and 17 and decommissioned version 10.

A lot of fine-tuning

We’ve made a number of improvements to the operator, notably in the resolution of add-ons’ plan identifiers, as well as to its dependencies:

These enhancements are designed to help you get the most out of Clever Cloud as a complement to an existing Kubernetes infrastructure. If you have any questions or suggestions, feel free to contact us in our GitHub discussion area.

Blog

À lire également

Scalability: definition, horizontal vs vertical scaling and how autoscaling works

When traffic grows, you are usually offered two fixes. A bigger machine. Or more machines. Both assume that your application can make use of them, and that is not a given.
Engineering

From the Console to Terraform: import your existing Clever Cloud infrastructure as code (IaC)

Nobody starts with Terraform. You create your first application in the Console, add a PostgreSQL database with Clever Tools, then a Redis instance, a Cellar bucket, and a “temporary” staging environment that is about to turn two. One morning, the organisation has forty resources, and nobody can say why the production application runs on two M instances instead of one, or who changed that variable on a Friday evening.
Engineering

Configure SSO with Keycloak

To configure single sign-on (SSO) with Keycloak, deploy Keycloak as an identity provider, then create a dedicated realm separate from master and a client for each application.
Features