Qovery at the Open Source Experience Event in Paris
What is the Open Source Experience?
Supported by Systematic Paris Region, the Open Source Experience is the meeting place for the entire open-source software industry, bringing together more than 4,500 professionals over two days! A place for technological exchanges, meetings, and business opportunities dedicated to open source and to all the players in the open source sector.
Open Source Experience focuses on open source technologies, solutions, and challenges in France and Europe. It highlights the driving role of open-source innovations in the digital transformation of companies in technologies such as AI, IoT, Cloud, and Blockchain.
Talks
During this event, you will be able to enjoy plenty of talks with a panel of speakers coming from inspiring companies and while here is the list of all the talks, let me give you a glimpse of what you can find:
- Secure multi-cloud deployment by Tony Jarriault - Cloud architect - SOGETI
- Honey, I Shrunk the cloud cost by Yannig PERRE - Administrateur système - AIOS
- Open Source, the appropriate response to societal and environmental issues by Charline Rageade - Accompagnatrice du changement | Ecologeek | Un pied dans l'agilité et l'autre dans le libre - Algoo
A Top-Notch Round Table
Whether it’s about securing multi-cloud deployment, hyperscaling platform and technology independence, database management in a fast-growing SaaS start-up, and much more, it will be the right place to come and get advice from one of the 80 open source experts and exhibitors that will be present at the event!
But that’s not it; discover the conferences of the track "Cloud, Multicloud & vendor-free, DevOps" with Romaric Philogène (Qovery) and Arnaud de Bermingham (Scaleway), which will be the track leaders for the event.
The conference also includes a top-notch round table with:
- Guillaume Laforge, Developer Advocate for Google Cloud Platform and Co-founder of the Apache Groovy programming language
- Sebastien Stormacq, Principal Developer Advocate at Amazon Web Services
- David Pilato, Devrel at Elastic for 10 years now, organizer of several events such as Devoxx
- Tugdual Grall, Solution Engineer at GitHub
- Julien Dubois, Principal Manager, Java & JavaScript Developer Advocacy at Microsoft and Creator of JHipster
Want to come?
Of course, we would love to see you there; make sure you are available on the 9 or 10 of November in Paris and grab your free invite. Don’t hesitate to drop us a line if you’re coming and are planning to meet us there. 💜
.svg)
.svg)
.svg)
Suggested articles
The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.
The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The structure, table, tool list, and code blocks are all worth keeping. The main work is fixing AI-isms in the prose, updating the case study to real metrics, correcting the FAQ format, and replacing the CTAs with the proper HTML blocks. The tool descriptions need the "Core strengths / Potential weaknesses" headers made less template-y, and the intro needs a sharper human voice.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
.webp)