Cloudera Docs

Release 3.3.0

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

New features

Automatic SSL context provisioning for secure inter-cluster communication

Cloudera Flow Management Operator for Kubernetes now automatically provisions a DefaultNodeSSLContextService in the root process group of each NiFi cluster. The service uses the existing node keystore and truststore, enabling secure TLS communication between NiFi clusters managed by the same operator without requiring manual SSL configuration.

Apache Ranger authorization support for NiFi

You can now configure NiFi deployments managed by Cloudera Flow Management Operator for Kubernetes to use Apache Ranger for centralized, policy-based access control.

Rolling upgrades for NiFi 2 version upgrades

Cloudera Flow Management Operator for Kubernetes now supports rolling upgrades between NiFi 2 versions. During the upgrade, at least one NiFi node remains running at all times to maintain service availability.

The upgrade behavior varies by scenario:

  • Upgrades between NiFi 2 versions: Configuration changes and version upgrades, such as 2.3.1 to 2.6.0, use a rolling upgrade.

  • Upgrades between NiFi 1 versions: Configuration changes that do not change the NiFi version use a rolling upgrade. Version changes require a non-rolling upgrade, during which all nodes are taken offline simultaneously.

  • Migration from NiFi 1 to NiFi 2: The migration always uses a non-rolling upgrade.

Declarative flow deployment using the ProcessGroup custom resource

The Cloudera Flow Management Operator for Kubernetes introduces the ProcessGroup custom resource for deploying NiFi flows declaratively. It imports a Flow Definition JSON from a Kubernetes ConfigMap or Secret into a root-level process group, starts the flow automatically, and records the process group identifier in the custom resource status.

Limitations:

  • Deployed flows cannot be updated.
  • Changes to the source ConfigMap or Secret are not applied after deployment.
  • External parameter contexts are not supported. Parameters must be defined within the Flow Definition JSON.
Automatic cleanup of unused operator-managed resources

Cloudera Flow Management Operator for Kubernetes now automatically removes Kubernetes resources that are owned by a NiFi or NiFi Registry instance but are no longer required after an operator upgrade or configuration change. During reconciliation, the operator identifies and removes these obsolete resources, helping maintain a clean cluster state.