Operator to generate k8s deployment manifests

[pavolloffay]

The operator could be used as a command line tool to generate k8s resource files based on supplied CR. So instead of posting objects to k8s API it would flush them to a file or standard output.

The main motivation behind this is to deprecate https://github.com/jaegertracing/jaeger-kubernetes. During the release process we could generate and publish the template for target deployments - all-in-one.

Example execution:

./jaeger-operator generate --cr cr.yml --output resources.yml

[jpkrohling]

This needs to come with very good test coverage in the form of end-to-end tests, so that we don't end up on a situation where we spend more time manually testing the output than the time that was spent writing the code.

[jpkrohling]

I think this could be a second binary, possibly published as a separate container image. Should be a fun feature to work on :-)

[chlunde]

Wouldn't the end-to-end tests for jeager-operator itself be enough?

And would it not share enough code that it could just be the same image? I can whip up a quick POC.

[pavolloffay]

Wouldn't the end-to-end tests for jeager-operator itself be enough?

I am also keen on testing this - at least for all-in-one deployment type.

And would it not share enough code that it could just be the same image? I can whip up a quick POC.

It would share most of the code. It depends on how intrusive it would be to the current main. A separate build might be better if this is considered a lower priority feature.