Technologies

Kubernetes and platform engineering

I'm a Kubernetes consultant and platform engineer in London. Intahnet Solutions is my UK Kubernetes and platform consultancy, so you deal with me directly, from the first message to the handover.

If your team runs Kubernetes (K8s), it is often the part of the setup the fewest people understand, because one person built it and everyone else deploys to it. I build, upgrade, review and repair Kubernetes and OpenShift clusters in production.

What I do

  • Cluster reviews. How the cluster is built, deployed to, upgraded and backed up, with the risks in priority order.
  • Upgrades. Including the cluster that is several versions behind and making everyone nervous.
  • Helm and GitOps. Charts your team can edit, and deployments through FluxCD or Argo CD in place of kubectl by hand.
  • Right-sizing. Finding the workloads that request far more CPU and memory than they use, and the ones that have too little.
  • Backup and recovery with Velero.
  • Troubleshooting. Pods that keep restarting, an ingress that drops requests, certificates that expire by surprise.
  • Docker and containers. Dockerfiles, images and the move from servers to containers.
  • OpenShift. Designing and building clusters, on your own servers or on AWS.

Platform engineering

Platform engineering means building the shared platform your developers deploy to, so each team stops re-solving deployment, secrets and networking on its own. In practice that is GitOps with FluxCD or Argo CD, Helm charts teams can reuse, Terraform modules in place of one-off setups, and a written path for adding a new service.

What I'd look at first

  • Whether pods have resource requests and memory limits, so one busy service can't starve or evict the others.
  • Which version the cluster runs, and whether it is still supported.
  • Where the secrets live, and who can read them.
  • What happens when a node fails.
  • Whether a restore has ever been tested.

Kubernetes or something simpler?

I recommend the setup that suits your team and your workload, and sometimes that is simpler than Kubernetes. Either way, I can help you get there.

What it costs

A Kubernetes cluster review starts at £1,500. For upgrades, repairs and platform work, I look at the cluster first and then quote a fixed price. See all prices.

I take on Kubernetes work as an ad hoc job, fractional DevOps days each month, a contract or an audit, on site or remotely across the UK. I write about infrastructure at hamzahkhan.com. Get in touch.

Questions

Which kinds of Kubernetes do you work with?

Kubernetes on AWS and Google Cloud, OpenShift on your own servers or on AWS, and clusters you run yourself.

Do you offer ongoing Kubernetes support?

Yes, as regular days each month or on contract. Tell me what cover you need.

Tell me what you need

A problem, a project or a role you're filling. Describe it in your own words and I'll reply within one working day.