Kubernetes Consulting
Design, implementation and operation of Kubernetes, when it is really needed. In the cloud with EKS, GKE and AKS, in the datacenter with OpenShift, at the edge in industrial plants with k3s and MicroK8s. GitOps releases, security, maintenance procedures, costs and, in the end, a team able to run everything on its own.
When you need Kubernetes consulting
Kubernetes answers specific needs: automating releases and the application lifecycle, handling high availability, meeting the requirements of off-the-shelf applications, which by now run on Kubernetes.
That is exactly why it pays to start on the right foot. Kubernetes is powerful, but it brings complexity with it: a badly designed cluster, or one adopted when there was no need for it, costs time and attention for years.
First whether, then how
The first thing we talk about is whether adopting Kubernetes makes sense in your case. The answer is not always yes: for a simple application, or for a team that has no way to look after it, it can be complexity that does not pay off. The same goes for add-on components, a service mesh for example: useful in some cases, a needless cost in many others.
If you decide to go ahead, you need to choose an adoption model:
- Multi-tenancy or multi-cluster. A single cluster shared between teams and environments, separated with namespaces and permissions, or several distinct clusters per environment, team or site. Isolation, costs and the effort of running them all change.
- Managed or self-hosted. A managed service such as EKS, GKE or AKS takes on most of the control plane work, while a self-hosted cluster, with OpenShift, k3s or MicroK8s, leaves more control in your hands.
What I do
The requests I receive most often as a Kubernetes consultant fall into these areas:
- GitOps with Argo CD. A single, reliable and traceable way to take applications to production: the desired state of the cluster lives in a Git repository, and Argo CD takes care of applying it.
- Maintenance procedures. Version upgrades, backup and restore, node management: written, repeatable procedures instead of a one-off intervention every time.
- Edge and IoT rollouts. Deploying and maintaining applications across dozens of remote sites, where hardware is limited and connectivity is not guaranteed.
- Security. Hardening the clusters: authentication, RBAC, secrets management, network policies, separation of environments.
- Observability. Full visibility into operations and into how the applications behave.
Kubernetes in industry and IoT
A growing part of my work involves industrial companies and IoT startups: Kubernetes in the datacenter, often as their first cloud native architecture, and in the plants, at the edge, where hardware is limited and connectivity uncertain. It is a context with specific challenges.
A team that knows how to run Kubernetes
A well-built cluster is not enough if the team cannot then get its hands on it. That is why knowledge transfer is always part of my work: mentoring on real problems, reviewing decisions, and when needed a Kubernetes course that brings the whole team to a common baseline.
Frequently asked
Does a small company really need Kubernetes?
Not always. It makes sense when there are several services to release frequently, high availability requirements, or off-the-shelf applications that already run on Kubernetes. For a simple application it risks being extra complexity that does not pay off. That is why the first thing we talk about is whether, in your case, adopting it makes sense at all.
Is managed Kubernetes better than self-hosted?
In the cloud a managed service such as EKS, GKE or AKS removes most of the operational work, and it is almost always the right choice. In the datacenter, on the other hand, you install and run it yourself, for example with Red Hat OpenShift. At the edge you need lightweight distributions such as k3s or MicroK8s, suited to the hardware and connectivity available on site.
We need to migrate away from ingress-nginx: can you help?
Yes. I have led migrations from ingress-nginx to Gateway API with Envoy Gateway, including the integration with cert-manager for certificates.
Do you also offer Kubernetes training?
Yes: a four-day course, theory and hands-on practice, that starts from containers and gets to day-to-day operations. It adapts to the company's stack.
Do you also work on Kubernetes at the edge?
Yes, and it is among the requests I receive most often. In industrial plants the hardware changes and, above all, so does the connectivity: you need lean distributions such as k3s or MicroK8s, and applications designed without taking a stable link to the datacenter for granted.
Other services
- Kubernetes for Industry and IoTKubernetes for industry and IoT: datacenter and plant platforms, lightweight distributions and application architectures built for unreliable connectivity.
- Observability and OpenTelemetryObservability with OpenTelemetry: incremental adoption, open source backend, alerting with Prometheus and a platform ready for AI agents.
- DevOps ConsultingDevOps consulting: reliable releases, infrastructure as code, cloud costs under control and a platform ready for AI agents.
- Platform EngineeringPlatform engineering: building a self-service, declarative and observable platform that people and AI agents can change safely.
- Kubernetes, Terraform and DevOps TrainingKubernetes, Terraform, Git and Security courses for technical teams: hands-on, on site or remote, with a dedicated lab and a tailored program.
- Cloud ConsultingCloud consulting: architecture and infrastructure on AWS and Google Cloud, hybrid setups, incremental migrations and cloud repatriation.