Helm chart

[heywoodlh]

Proposed changes

This adds a Helm chart so that Nuclei can be deployed easily in a Kubernetes cluster.

Checklist

I don't think that testing is super essential with these changes, but I suppose it could be implemented with helm template .. If there is interest to implement this as a test I can add it.

• [x] Pull request is created against the dev branch
• [ ] All checks passed (lint, unit/integration/regression tests etc.) with my changes
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] I have added necessary documentation (if appropriate)

[heywoodlh]

Documentation PR is here: https://github.com/projectdiscovery/nuclei-docs/pull/67

[heywoodlh]

Some things I'd like to note:

• Using the Helm chart as its base, I was able to write a Helm chart at my place of employment that automatically scans all our web applications in our cluster. I think Nuclei's flexibility puts it in a unique position to fill the need of network-level vulnerability scanning and fit very nicely into Kubernetes. I have found that most Kubernetes-focused vulnerability scanners only focus on the OS and package level within containers. Nuclei could very much fill that gap in a lot of Kubernetes deployments, imo.
• The Helm chart at the moment has no method of persistence for Nuclei templates. So the Helm chart is wholly dependent upon the community templates. I'll probably update the chart with this functionality sometime this week.
• Something like Mend Renovate should be implemented to automatically keep the container image tags up to date in the values.yaml file

[ehsandeep]

@heywoodlh thank you for sharing this.