GitOps has quietly become the backbone of modern platform engineering.
According to the State of Platform Engineering (Vol. 4), 56.5% of platform teams now rank GitOps as a top-four capability, right next to CI/CD, Infrastructure as Code, and Kubernetes itself.

And yet… most training still treats GitOps like a developer convenience tool.

This course doesn’t.

This is GitOps as the orchestration layer platform teams actually build and operate.

GitOps at scale (aka: your clusters are not pets)

If you’re planning to go big, really big, and not just manage a handful of clusters you still remember by name, then you need to understand GitOps at scale.

Less shepherd with a stick.

‍

More fleet commander with god mode enabled.

You’ll learn how large enterprises design cluster topologies to manage thousands of locations across different regions, data centers, and clouds, without turning operations into chaos.

Less watching. More doing.

The best part?
You don’t just watch slides.

You fork the repo and work with an enterprise-ready setup, based on the general distro of kubara.io, a framework from platform engineers, for platform engineers, going open source very soon (March).

No wheel reinvention.
Just adapt it, run it, and move on with life.

Scaling is hard. Tool soup is harder.

Scaling has limits. Choosing the wrong topology means you’ll end up with a random pile of tools and hope it works.

And sure, it might work.
A lot of my hobby projects still work too.

But hobby projects don’t get security audits.
Your platform will.

Platforms are not just tools.
They are people, culture, and adoption.

GitOps adoption takes time.

It hurts.

Your developers might cry at first.

But later, they’ll cry tears of joy when they realize their best disaster recovery plan is a GitOps setup that keeps everything reconciled, while you’re in the Bahamas, drinking a Cuba Libre and swimming with pigs.

(This is Peter. Not me.)

Real talk: does this actually work?

Yes. Last project.

We managed:

• 30 clusters
• 300 VMs
• 20+ projects
• hybrid setups across multiple data centers and public clouds

With 2.5 engineers.

Onboarding a new project?
Under 30 minutes.
Compliant. Budgeted. Integrated.

So yeah… I do know what a Cuba Libre tastes like. Maybe.

What’s in the course?

Module highlights:

• Foundations & principles
  GitOps as a contract between humans and agents, not just “CI/CD with Git”
• Architecture & patterns
  Multi-cluster topologies, progressive delivery, and avoiding classic anti-patterns
• Tooling deep dive
  Hands-on with Argo CD, Flux CD, and Sveltos, including a platform catalog for self-service
• Enterprise scaling
  Managing 1,000+ clusters, trying to scale to 15,000 clusters, policy-as-code, and solving config sprawl
• AI integration
  GitOps for AI platforms and AI workloads
• Cultural adoption
  Stakeholder buy-in, shared language, and iteration based on feedback

Plus an exclusive interview with Alexis Richardson, founder of RabbitMQ, CEO at ConfigHub, and the person who coined the term GitOps in 2017.
No vendor fluff. Just history and real-world perspective.

The best part?

The course is FREE.

Well… not exactly free.
You invest time. That’s it.

Who am I?

Artem Lajko.
Course instructor.
Head of Platform Engineering at iits.
Author of Implementing GitOps with Kubernetes.
A few years of building GitOps platforms across different industries.

If you’re curious about GitOps at scale,
want to chat, learn how a Cuba Libre tastes,
get a free signed book,
or maybe even win a Steam Deck. Come say hi at KubeCon EU in Amsterdam!
24–26 March | Booth #495 (iits)