☸️ Create a native Tiled Kubernetes Operator

[Kezzsim]

Around 2020 Kubernetes spec introduced the Operator Pattern for creating YAML that can manipulate many different types of cluster resources and include provisions for scaling and adapting to different scenarios automatically.
(Capitalizing the O is important, it differentiates between an operator [human who manages the cluster] and the automated spec)
Since then development of Operators has followed a similar pattern to Helm charts, providing a simple way to 'install' cluster resources containing specific container images to run as a service. Namely in the wild, a helm chart mainly specifies creating a stateless deployment of a service into an extant cluster, whereas Operators are more often associated with stated applications that include other resources like persistent volume claims e.g.

Presently there exists a Tiled helm chart created by @DiamondJoseph which is useful for provisioning a standard Tiled deployment, however as work on the NSLS-II NEXT-III and N3XTWARE initiatives has commenced we've found use for deploying Tiled on a stateful set and including other resources by default like a Postgres instance, PVC for artifact storage that mounts our institution's NFS, etc.

What is the general consensus on creating a Tiled operator that can be pulled from OperatorHub when needed?