Michael H

This still happens with rook 1.14.3 and ceph 18.2.2. I have only seen it happen on clusters with 1 control plane.

> > This still happens with rook 1.14.3 and ceph 18.2.2. I have only seen it happen on clusters with 1 control plane. > > which OS version is being...

> upstream fix is here: [ceph/ceph#57969](https://github.com/ceph/ceph/pull/57969) Awesome!! Thank you. Any chance this could be applied to `reef`?

I see `nifi.queue.backpressure.count` and `nifi.queue.backpressure.size` in `nifi.properties` to change the default backpressure object and data size settings. However, i don't see a way to change the default flowfile expiration at...

Ah okay so perhaps this would be an addition to a `NifiDataflow` to include defaults for these properties. Then if the properties aren't explicitly configured in a versioned flow in...

One option might be to create a [kubectl krew plugin](https://github.com/kubernetes-sigs/krew) to contain all of the utilities needed to quickly inspect and change NiFi cluster deployments. Initially, i had thought we...

@Demcheck : The error you're encountering is in the logs you shared. > "could not create secret with jks password: secrets "nifi-cluster-3-server-certificate" already exists" Delete `nifi-cluster-3-server-certificate` secret and nifikop will...

Did you look at cert-manager logs to see if there are issues there? And did you follow the guide here? https://konpyutaika.github.io/nifikop/docs/v1.0.0/3_manage_nifi/1_manage_clusters/1_deploy_cluster/4_ssl_configuration

If you insist on using self-signed certs, I would recommend using a common CA to sign the certs for Registry and NiFi. For example, create a self-signer CA independently of...

Was this logback.xml just copied from the 2.0.0-M1 baseline?