Hey team! Can I ask what is your take on Druid Operator? Is it mature for production use? I am thinking of migrating Druid from EC2 VM instances to Druid Operator as a means for better scalability and cutting down costs, as EC2 instances scaling is not so great. For example, having to scale from r7i.4xlarge to r7i.8xlarge at some point in time represents an almost double in cost while (I hope) with K8s and Druid Operator we can just reserve just some more memory. What is your experience and what do you think about that? (edited) Also there are 2 Druid Operators available. • druid-io/druid-operator • datainfrahq/druid-operator Anyone knows what are the differences? In OperatorHub I only see the latter

The main difference between those two is druid-io / druid-operator has a deprecation notice at the Readme:

# Deprecation Notice: 
- Refer to <https://github.com/druid-io/druid-operator/issues/329>.
- The project will be externally maintained in the following fork [druid-operator](<https://github.com/datainfrahq/druid-operator>)