kubebuilder vs operator sdk vs ...

[emaxerrno]

https://www.openshift.com/blog/operator-sdk-reaches-v1.0

[emaxerrno]

@dimitriscruz @alenkacz @RafalKorepta

[emaxerrno]

@dotnwat - i think that kubebuilder became the low level infra for operator sdk which is interesting.

FYI: @rkruze @BenPope
cc: @Mateoc @andresaristizabal @0x5d @mmaslankaprv

[RafalKorepta]

We can aim to integrate with OperatorHub as nice to have feature. The main focus is to have working controller with the polished CRDs.

[dotnwat]

Yes. I recall chatting with @alenkacz about this topic -- that kubebuilder as a base layer, and other projects offering different abstractions on top, or one can use kubebuilder directly. i'm sure it is more nuanced, tho.

[alenkacz]

I personally would go with kubebuilder to scaffold the project and if we end up needing something from operatorsdk later we can always add that on top.

Oh I love that they mention using https://kuttl.dev/ for testing which is project we've been working on for the last 2 years :) opensource FTW!