Enhancement: Official Helm chart for GitOps installation

Our team at CERN deploys its applications on top of Kubernetes using ArgoCD, following GitOps practices. We apply the same approach when deploying the Oracle Database Operator. But because configuring the Operator requires a few additional scripts and commands, it cannot be reconciled straight from your Git source.

In version 2.2.0, the scripts/generate-namespace-install.sh script essentially acts as a template engine, generating WATCH_NAMESPACE and the per-namespace RoleBindings from a namespace list. The difficulty for us is that ArgoCD can't run it during rendering, so we have to execute it out-of-band, commit the output into our own repo, and regenerate it on every upgrade.

Helm can replace the custom script with a a native Kubernetes templating engine. Helm also integrates nicely with ArgoCD, that can render it natively from the values in Git at sync time.

An official Helm chart supported by Oracle would help users :

• install and configure the Operator with no scripts or manual steps
• use chart hooks to specify creation/deletion order, and simplify upgrades
• toggle namespaced vs cluster-wide as a single value
• manage WATCH_NAMESPACE and the creation/deletion of RoleBindings from one list

For reference, another Oracle project, oracle/coherence-operator already does something similar (watchNamespaces, onlySameNamespace).

Start with scripts/generate-namespace-install.sh and compare its generated WATCH_NAMESPACE and per-namespace RoleBindings with the existing Kubernetes manifests. Review the referenced oracle/coherence-operator approach, then define an official Helm chart whose values cover namespaced or cluster-wide installation, namespace watching, RoleBindings, and upgrade ordering; done means ArgoCD can render and reconcile the installation without manual scripts.