A manufacturing group’s IT landscape on Kubernetes
We brought the company’s internal services together into one cluster: mail and chat, the knowledge base, equipment records, storage, secrets. The state of the cluster is described in a repository, and deployment runs through GitOps.
Problem
The internal services had multiplied and each one lived by its own rules: different servers, manual installation, and nobody could say what was running where or how to reproduce it. Every update turned into an investigation.
Services scattered around and installed by hand
No single description of what is running
Reproducing or updating a service is slow and risky
Solution
We consolidated the services into one cluster and described its state in a repository. Changes arrive through git rather than through manual work on the servers.
A single k3s cluster on Hetzner servers
Cluster state described in a repository
Deployment and rollback through ArgoCD
Certificates, ingress and secrets in one shared setup
Stack and tools
Hetznerk3sArgoCDPostgreSQLMinIO
Results in numbers
15
services in one cluster
1
repository describes the entire state
0
manual installations on servers