Blog Entries

30. 09. 2025 Marco Berlanda Development, DevOps, Kubernetes

A GitOps Path from Code to OpenShift Cluster

A modern web app isn’t one single big monolith: it’s made of quite a lot of pieces! For instance, we relied on a setup such as this one for a recent one we are developing: That’s a lot of moving parts. You could glue them together with scripts, sticky notes, and caffeine… but then most…

Read More
30. 09. 2025 Luigi Miazzo DevOps, Kubernetes

Envisioning Satellite-Distributed Management with Kubernetes and Argo CD for NetEye.cloud

As our company’s NetEye cloud solution NetEye.cloud expands, we’re deploying compute nodes not only in our own data centers but, on customer premises across the globe – connected through satellite links. This hybrid, geo-distributed model creates a very tough challenge: How can we manage configuration across hundreds of remote machines reliably, and at scale? Why…

Read More
16. 09. 2025 Davide Sbetti DevOps, Kubernetes

Monitoring DBs through PMM: a Migration to OpenShift

Hi 😀 Today I’d like to explore with you a migration that we performed to a service that’s used internally to monitor the performance of various DBs, gathering data that’s especially useful for troubleshooting. This tool is the Percona Monitoring and Management (PMM) platform, which combines agents or direct access to various supported DBMS (MySQL,…

Read More
05. 08. 2025 Alessandro Valentini DevOps, Kubernetes

Use S3 Storage with OpenShift Data Foundation

Recently, we needed to upload build artifacts to allow developers to visualize Playwright test recordings. Initially, we used a simple PVC and an NGINX server with basic authentication, but this approach has a major drawback: it doesn’t allow uploads from different namespaces. As a result, we had to choose whether to deploy this service and…

Read More
30. 06. 2025 Alessandro Taufer DevOps, Kubernetes

How to Replicate Sealed Secrets in Multiple Namespaces

One of the most annoying aspects of using Sealed Secrets is their encryption design. They are tightly coupled to the namespace and name of the target Secret, meaning any changes to either require re-encrypting the Sealed Secret. This rigidity complicates workflows, especially when you need to duplicate or promote Secrets across environments. It breaks the…

Read More

Archive