Alena Varkockova

@pvsune looking at the minimal CR ``` tls: enabled: true secretKeyRef: name: my-console-tls namespace: default ``` should we rename secretKeyRef to nodeCertSecretKeyRef or something ... or how do you expect...

@danepowell just out of curiosity, if you suspect it's tiller, did you try to run the same against helm3?

Oh yeah, I need this as well :D beware that some part of this was already described in this KEP https://github.com/kudobuilder/kuttl/blob/main/keps/0006-lifecycle.md just for reference (we don't need to follow that...

I believe that kuttl cleans only the namespace in which the tests are run. Any reason why you're creating pod in a different namespace?

is there a way I can help to move this forward?

@timoreimann After looking at the code, these are my thoughts... - keep old and new set and get methods for networks and ports - by using either of them, set...

@timoreimann good point, but I would not be concerned about that. With minor updates between versions there are usually zookeeper migrations involved so you would not want to have both...

@timoreimann well the version would have to be negotiated for a single connection and there is no way that you can switch versions without losing a connection to that node......

@timoreimann on a second look I unfortunately don't think there is a good way to do this in a backward compatible manner :( Currently this client API is very tightly...

@timoreimann yeah I got to the same conclusion looking at the code - since getting version before the request means doing two separate request, we are not guaranteed that it...