NDB Operator 0.0.7 upgrade

[akshmish]

• Using k8s manifests to build a helm package
• Importing the required YAML changes for Helm Chart release, from the output of "make deploy" command
• Moved CRDs (DB, DBServer to /crds), deleted "Namespace" file
• Adding Templating logic to YAMLs

[manavrajvanshi]

Please also update the Readme

[akshmish]

Left some comments around the templating, can we do the following:

Deploy the operator via Helm with a non-default name and non-default namespace to check if things still work correctly. (Example - test-operator, test-namespace)

I feel that some services created for/by the webhooks might be using some selectors and labels that use the names/namespaces. Since we've created the charts using kustomize, these fields are hardcoded to "ndb-operator" in certain places, which might be different than the name being provided during the deployment of the operator via Helm.

I might be wrong, but we can test this by deploying the operator via the Helm chart using different name/namespace combo and see if it works.

What do you guys think? @akshmish @tuxtof

Sure, I am working on testing this scenario. Initial testing worked with a different name and a namespace.