Thread by @iximiuz

The idea of Kubernetes Operators is simple and attractive.

But as it usually happens, the devil is in the details. I've been working on an operator for the past few weeks, and the learning curve is quite steep, actually.

Here are some projects that may help 🔽

1. kubernetes-sigs/kubebuilder

GitHub says it's an "SDK for building Kubernetes APIs using CRDs."

But you can scaffold an operator project with it.

2. operator-framework/operator-sdk

Much like kubebuilder, this project allows you to scaffold an operator real quick.

The difference is that it comes with batteries included:

- support of Ansible and Helm operators
- simplifies releasing operators (OLM)
- e2e testing
- linting

3. kubernetes-sigs/e2e-framework

An experimental e2e testing framework for Kubernetes clusters.

With the simple `go test` command you can deploy your operator, create customer resources, and validate the logic.

4. kubernetes/client-go

That's how you call the Kubernetes API. Must-have for learning.

5. kubernetes-sigs/controller-tools and kubernetes-sigs/controller-runtime

Both, Kubebuilder and the Operator SDK are based on these two lower-level projects.

Worth checking out to understand the internals.

And if you still don't understand the idea behind the Kubernetes Operator, check out this illustrated introduction

iximiuz.com/en/posts/kuber…