Release 2.10.0

New features

Cluster scheduling

The NiFi custom resource now contains a schedule spec that can be used to define the times during which the NiFi cluster should be running.

Security providers

In order to support FIPS compliant operation, a method of providing and declaring additional Java security providers, such as CryptoComply for Java and Bouncy Castle, has been added to the NiFi spec.

OIDC authentication

Support for OpenID Connect authentication has been added to the NiFi Registry spec.

Out of memory (OOM) recovery

An OOM Recovery function has been added to the NiFi controller. When configured, the CFM Operator will detect OOM events in NiFi and increase the memory of the Pod by a configurable step.

Additional proxy hosts

A NiFi spec field has been added such that multiple hostnames can be provided to NiFi. This allows configuration of alternate DNS names for the NiFi service beyond the hostName spec field.

NAR volume providers

Provide NiFi NARs through Kubernetes volumes. NARs can be landed in a networked filesystem or object storage and provided to NiFi by way of a CSI driver, i.e. EFS or S3.

Additional CA bundles reference

Additional CA certificates can now be provided by a Secret or ConfigMap reference instead of in-line in the NiFi spec yaml, greatly reducing file length and improving readability.

Environment variables

An environment variable override has been provided in the NiFi spec. This allows for setting custom environment variables on the NiFi container for use in Flows or Python scripts.

Fixed issues

• NiFi Registry resources not cleaned up on delete, i.e. PVCs and Certificate Secrets.

• NiFi Registry hostname not added to Node Certificate.

• NiFi Registry users and authorizations incorrectly persisted.

• NiFi not restarting when additional CA bundles are provided.