<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Nicolas Massé</title><link>https://www.itix.fr/opensource/kubernetes/</link><description>Recent content in Kubernetes on Nicolas Massé</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 05 Nov 2024 00:00:00 +0200</lastBuildDate><atom:link href="https://www.itix.fr/opensource/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Behind the scenes at Open Code Quest: how I implemented the Leaderboard in Red Hat Advanced Cluster Management</title><link>https://www.itix.fr/blog/behind-the-scenes-at-open-code-quest-how-i-implemented-leaderboard-with-acm/</link><pubDate>Tue, 05 Nov 2024 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/behind-the-scenes-at-open-code-quest-how-i-implemented-leaderboard-with-acm/</guid><description>&lt;p>After revealing the behind-the-scenes design of the Leaderboard for the &amp;ldquo;Open Code Quest&amp;rdquo; workshop during the 







&lt;a href="https://www.itix.fr/speaking/red-hat-summit-connect-france-2024/">

Red Hat Summit Connect France 2024

&lt;/a>



, it&amp;rsquo;s time to delve deeper into its practical implementation!&lt;/p>
&lt;p>In this article, I&amp;rsquo;m going to take you through the configuration of &lt;strong>Red Hat Advanced Cluster Management&lt;/strong> as well as the various adaptations needed to connect the &lt;em>Leaderboard&lt;/em> created earlier with the &lt;strong>Open Code Quest&lt;/strong> infrastructure.&lt;/p>
&lt;p>Come on board with me for this new stage, which is more technical than the previous one, as I had to get creative to wire up a very &amp;ldquo;conceptual&amp;rdquo; Grafana dashboard with the reality of OpenShift clusters!&lt;/p></description></item><item><title>Build multi-architecture container images with OpenShift, Buildah and Tekton on AWS</title><link>https://www.itix.fr/blog/build-multi-architecture-container-images-with-kubernetes-buildah-tekton-aws/</link><pubDate>Thu, 02 May 2024 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/build-multi-architecture-container-images-with-kubernetes-buildah-tekton-aws/</guid><description>&lt;p>In 2022, I wrote an article on this subject named 







&lt;a href="https://www.itix.fr/blog/build-multi-architecture-container-images-with-kubernetes-buildah-tekton-and-qemu/">

Build multi-architecture container images with Kubernetes, Buildah, Tekton and Qemu

&lt;/a>



.
The article described the configuration I had set up for my personal projects.
It even went beyond its initial purpose as it has also been used by several colleagues at Red Hat who had the same need.
While the configuration described in this previous article is still relevant, the approach is somewhat dated.
With the increasing availability of ARM servers in the Cloud, I revisited the topic of building multi-architecture container images using the AWS cloud.&lt;/p></description></item><item><title>Build multi-architecture container images with Kubernetes, Buildah, Tekton and Qemu</title><link>https://www.itix.fr/blog/build-multi-architecture-container-images-with-kubernetes-buildah-tekton-and-qemu/</link><pubDate>Wed, 24 Aug 2022 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/build-multi-architecture-container-images-with-kubernetes-buildah-tekton-and-qemu/</guid><description>&lt;p>ARM servers are becoming mainstream (Ampere Altra server, Raspberry Pi SoC, etc.) and people start using them with containers and Kubernetes.
While &lt;a href="https://hub.docker.com/search?q=&amp;amp;image_filter=official">official Docker Hub images&lt;/a> are built for all major architectures, the situation is less clear for other Open Source projects.
It is possible to acquire an ARM server and use it to build container images, but it puts an additional constraint on the Continuous Integration chain.
This article explores another option: build ARM container images on a regular x86 server, using Kubernetes, Buildah, Tekton and Qemu.&lt;/p></description></item></channel></rss>