Release 3.4.0

The Nifi custom resource is now available at API version cfm.cloudera.com/v1, reflecting its maturity as the default version for new deployments. Version v1alpha1 remains supported for existing clusters, but new spec fields are added only to v1.

For more information, see Group, version, kind, meta.

Cloudera Flow Management Operator for Kubernetes supports deploying NiFi 2.11 container images. For supported component versions, see Component versions.

You can configure a list of namespaces for Cloudera Flow Management Operator for Kubernetes to reconcile during installation. When you do not set this list, the operator continues to watch all namespaces, which is the default behavior.

For more information, see the watchNamespaces property in Helm chart reference.

Creation of RBAC resources for the operator, including ClusterRoles, ServiceAccounts, and bindings, can be turned off at install time. You can then define a stricter RBAC model and supply the roles and service account that the operator uses.

For more information, see the rbac.create and serviceAccount.create properties in Helm chart reference.

As a cluster administrator, you can assign a distinct Cloudera Flow Management Operator for Kubernetes user identity to each NiFi cluster. This scopes the operator identity that performs NiFi API management in that cluster.

The User, UserGroup, and ProcessGroup custom resources can no longer target a NiFi cluster in a different namespace. This preserves namespace permission boundaries that cluster administrators define, so principals without access to a namespace cannot use these resources to manage NiFi clusters or flows in that namespace.

The operator now guards against a nil user ID when adding or removing users from policies.