Helm based deployment

[alexku7]

Hello

Any chance to see a helm based deployment package?

We have many but relatively small clusters. Installing the OLM operator in order to install the node-healthcheck-operator is "kind of" overhead and resource wasting.

Helm installation package could be very useful.

[mshitrit]

Hi @alexku7, thanks for reaching out.

We lately had a similar discussion on our [email protected] , so feel free to check it out for more context.
I'm taking the liberty of quoting @slintes replay, which I think also applies here:

that's correct, all our operators are built with operator-sdk and depend on OLM for deployment.
Currently we don't plan or have the resources to add, maintain and test Helm support.

In this issue are some suggestions on how generate a helm chart for operator-sdk based projects: operator-framework/operator-sdk#4930 (comment)
The last comment points to the "helmify" project, which looks promising IMHO: https://github.com/arttor/helmify?tab=readme-ov-file#integrate-to-your-operator-sdkkubebuilder-project
Maybe you can give that one a try? Please let us know if that works, so we can add it to our docs at least.

[slintes]

here the link to the relevant thread, because the discussion is ongoing: https://groups.google.com/g/medik8s/c/_X5YVLQanLU/m/rbVRUwgGAwAJ

[ns-it-safadi]

Any update for this issue? Second question we have two steps in Makefile
make install
make deploy

Do these two steps are not enough to install NHO on ks manually?
Where first one installs crds
Second one generates manifests from config/default or config/manifests/k8s and apply them on cluster.

[clobrano]

Second question we have two steps in Makefile
make install
make deploy
Do these two steps are not enough to install NHO on ks manually?

These steps expect some configuration (related to RBAC) already in place in the cluster, which is something that OLM does

[ns-it-safadi]

Second question we have two steps in Makefile
make install
make deploy
Do these two steps are not enough to install NHO on ks manually?

These steps expect some configuration (related to RBAC) already in place in the cluster, which is something that OLM does

I checked the list of resources which are installed by (operator-sdk olm install),

https://olm.operatorframework.io/docs/getting-started/

So which of these CRDs are required to install (node-healthcheck-operator) without using OLM at all?

As I understand OLM, its and package manager, ( install, uninstall, update..etc). so no need to have it in case that I can deploy the same manifests using helm or any other way.
so Which resources are REQUIRED to run node-healthcheck-operator on K8S.

[clobrano]

Have you already had a look at https://groups.google.com/g/medik8s/c/_X5YVLQanLU/m/rbVRUwgGAwAJ ?
There was already some discussion about this there

[ns-it-safadi]

yes I did,it doesnt work :(

[clobrano]

There's definitely some work to be done, and unfortunately, we don't currently have the capacity to take it on. However, we're absolutely open to reviewing PRs and appreciate any contributions from the community.

[slintes]

any deployment method which doesn't use OLM, including make install / make deploy, won't work without configuration changes for certificate setup, needed for webhooks.

[ns-it-safadi]

Where could we find such configuration certificates setup? I guess that OLM generates and mounts them to the images on runtime, so where I can find these certificates configuration?

Second question: we couldn't make this process as a part of configuration for specific operator? so in case that it requires these certificates then operator has to add it as a secret or mount it somehow?

I believe that it's good to have info about resources installed via OLM for any operator.
When I installed this operator using OLM I saw a lot of resources installed. so nice to have such list of resrouces, CRDS, RBACs, TLSes ..etc.

for now, where can I find cert configuration?

[slintes]

Where could we find such configuration certificates setup?

look for [WEBHOOK] and [CERTMANAGER] in the /config directory. But this wasn't used or tested for years...

resources installed via OLM

see bundle/manifests directory