Rakesh Bajpayee

Started Working...

Hello @jotak Is there anything you want me to work on regarding this issue?

Thanks @jotak .Got the idea, starting to work on the ArtifactHub publishing template. I think It required a much more dynamic chart than it is right now. Share your thoughts...

> Now, the part that I'm less familiar with, is ArtifactHub. If I'm correct, this is the go-to solution for anyone who want to publish helm charts, right? Maybe you're...

Hello @jotak , I regret my absence to participate in those contributions; now I have started working on these two things. > * Fill out the chart dependencies? (https://helm.sh/docs/topics/charts/#chart-dependencies): it...

> The CRD itself is not namespaced, but the webhook definition, that is part of the CRD, depends on the namespace where the operator is installed, see here: https://github.com/netobserv/network-observability-operator/blob/main/helm/templates/flows.netobserv.io_flowcollectors.yaml#L11-L18. That's...

> It can be configured in the Chart.yaml file to enable or disable the installation of the dependencies, and also we can toggle the value during installation. I will add...

As most of the k8s operators uses a default pre-defined namespace for deployment and ```netobserv``` namespace is also fitting with with the name of this application my thoughts are that...

Done the further 2 steps, 1. Using a workflow to update those image values on every upgradtion. 2. Writting a description and additional instruction about this helm release in NOTES.txt

> Hi @Helion55 I'm getting errors with the namespace "netobserv" not found. I suspect there must be issues with the ordering of installations, e.g. if the namespace isn't created yet...