John Brownlee

Not quite. I would interpret #245 as being about the FDB pods that the operator launches, whereas this would be about the CLI commands run within the operator pod itself.

The idea is to pass the log group from the environment variable to the CLI commands, because I don't think they pick up the log group from the environment. I...

> Hm, that's interesting my test actually showed that the `LogGroup` was set but let me confirm that. In addition to that the env variable should already be passed down...

I would only expect the operator to talk to FDB pods. However, if pod get rescheduled with different IPs, there could be components in the database that continue to try...

We used to have code in the operator to react to a CR being deleted and clear up the cache of the database connections, but we removed that cache because...

Deploying an instance in the operator to each namespace should work. If you're going that route, you would want to separate out the deployment of the CRD, since you only...

Ideally we should address this in the operator, by closing the connections automatically, but I'm not sure what that would entail.

This could be trickier, because the file name rules for client libraries are technically less strict, and we may only have a certain version's client library available as the primary...

Every FDB process has a public address (IP and port), and everything that connects to that process must be able to connect on that public address. Because of that, I...

We could try to attach something to the cluster resource to give an idea for which instance of the operator owns it. I think all we would have to go...