Making Operator part of a Helm Chart

[adrianhr91]

I've read through the Deployment docs, and while that method of deployment is convenient, it doesn't fit the nature of my project. I have a Helm Chart that bundles a few pieces of functionality together, effectively create a new namespaces and a bunch of deployments in it that work together to achieve my business logic.

We use fluxcd and already have a GitOps setup where a HelmRelease is automatically reconciled with our production Kubernetes cluster. I don't want to have the operator build and deployed separate from that.

I was thinking rather than relying on the existing functionality of the library, which makes the Dockerfile and deployment (+ all other resources) available at build time, I can just create my own Dockerfile, deployment, CRD etc. Then I can embed those in my Helm Chart. Once the Helm Chart gets installed, the operator will run and I'll start getting the benefits on this library!

Does that sound like a reasonable thing?
Are there any particular concerns and core concepts that I'm going against?
Is there an easier way to achieve what I need?

[kimpenhaus]

Hi @adrianhr91

I am for sure no pro on what's the best to do but we actually do the same. Handcrafted deployment, rbac and all that is needed tailored into a helm chart which gets deployed from a ci pipeline. For our needs this works perfectly.

If you want some more details please let me know, once I get back home I'll can provide.

Marcus

[adrianhr91]

thanks! I got something working as well, I just wanted to make sure I'm not going against a core principal of the library or something 😄