Michael Burman
Michael Burman
> I think you need to create new secrets for the sake of security, not re-use existing client secrets. This is not the correct way, as mgmt-api supports a single...
@bradfordcp ?
Right now the functionality is as intended. The users / superusers feature is intended to only enforce that those users set there are existing in the cluster (or if using...
Sadly making it immutable could prevent adding another dc which controls the username creation. And it wouldn't solve the issue really, you could still modify the Secret itself (which is...
There's no separate seed nodes in our system, the seed labels get targeted with an algorithm to available nodes such as the first starting one. The system should always have...
> Only one Pod came up and that's the only Pod with the seed-node label. This is as it should be, we only label seeds when they come up. The...
The CRD upgrader supports the airgap/offline installation method also, but that requires the version of k8ssandra-operator CRDs to be in the bundled file. This isn't happening for k8ssandra-operator chart file,...
You can set ``client.proxy`` to configure the HTTPS_PROXY used for the Helm access. https://github.com/k8ssandra/k8ssandra-operator/blob/main/charts/k8ssandra-operator/values.yaml#L101
It is possible, but would require you to build your own client image (which you can supply in the Helm values) with the k8ssandra-operator chart embedded. You can see the...
If you run the operator locally, you need to define where the configFile is (there's a cmdline parameter --config for that).