TPR name unclear about nats-operator HOT 3 CLOSED

Possibly some mess up when merging. Unfortunately, I haven't had the time to move forward with this implementation but would be great to have someone else helping out as well.

from nats-operator.

I'm working on a site that's basically a curated catalog of operators. I've also written the Memcached operator there and am working on the one for MongoDB (very early). My Go isn't very strong though, my own operators are in Python. I won't be much help due to my limited Go and the fact that I don't know anything about NATS.

I will give this TPR name issue a try though. That should be easy enough to fix. I would assume you agree that NatsCluster is the better name?

from nats-operator.

I would assume you agree that NatsCluster is the better name.

Correct. management.nats.io is or should be the API group, while NatsCluster is the API object.

I paused this work because of some TPR bugs. Need to check if they've been fixed or not.

from nats-operator.