How ready is this project to actually make an operator with it?

[EraYaN]

It seems like this would replace the main Reconcile function in a standard Operator SDK operator. How would we go about wrapping this into an actual k8s operator?

[iliapolo]

@EraYaN This project hasn't seen updates or received attention in a while, and is still experimental. We are definitely keeping an eye out and would appreciate any insight or ideas you may have.

[EraYaN]

I ended up using server-side-apply on our operator which sort of makes something like this unnecessary for us since the ApplyConfigurations are more than usable and clear in go. And it makes the API server deal with all the merging and patching.

[srgvg]

FYI

After writing out some dist/ structure generating code based on a custom yaml style "cluster stack" configuration file, I had a look at the operator to see if I could use it. The first bump I encountered:

• "Request body should include a single k8s resource in JSON format", (only vaguely mentioned at the end of the README.md) hence resulting in a single object single yaml file output.
• Quite some confusion about the need for input and output file, given this should work as a network server.

Working on a FluxCD bases system, in the end the generated contents from dist/ wil end up packaged as OCI artefact. My goal would be to have some network server accept a request body describing a "ClusterStack", and retrieving a tarball of dist/ or something that can then be uploaded as OCI artifact.