Release 3.0.0

Learn about the new features and notable changes in release 3.0.0 of Cloudera Flow Management Operator for Kubernetes.

New features

User CRD
This release introduces a new Custom Resource Definition (CRD) that represents a NiFi user and allows for defining a user identity and associated access policies.
NiFi deployments secure by default

NiFi deployed by Cloudera Flow Management Operator for Kubernetes is now secure by default. When no authorization method is provided, NiFi will be configured in single user auth mode with username "demonstration-user" and password "demonstration-password". When no Node Certificate Generation is specified, node certificates will be generated using a self-signed Cluster Issuer nifi-node-certs that is deployed with the operator.

Fixed issues

Lost flow during zero leader scale up

If a NiFi cluster lost all viable leaders during scale up (usually a single node cluster scaling to two nodes), the new Node would begin waiting for leader election, eventually time out, and declare itself the leader with an empty flow definition. When the old leader finally recovered, it would take the empty flow of the leader, assuming it had no data in queues. Cloudera Flow Management Operator for Kubernetes now temporarily reverts the scale up if there is no viable leader at any point in the scale up process.