Product Update: Cloudera Flow Management Operator for Kubernetes v3.1

[#1]

The Data In Motion Team is pleased to announce the release of Cloudera Flow Management Operator for Kubernetes version 3.1. This release introduces powerful new security and automation features, focusing on programmatic identity and access management, automated certificate generation, and intelligent cluster lifecycle enhancements that significantly reduce admin overhead and streamline user onboarding.

Release Highlights:

Programmatic User Group Management via UserGroup Custom Resource Definition (CRD): This new CRD enables admins to configure NiFi user groups directly in YAML. By managing user groups as code within the Kubernetes environment, it streamlines the organization of users, reduces manual configuration, and ensures consistent group management across clusters, significantly improving overall admin efficiency.

Streamlined Access Control with AccessPolicyProfile CRD: This new CRD allows admins to define sets of access policies and roles for users programmatically. By consolidating access policies into a profile, it simplifies the assignment of permissions, ensures security policies are consistently enforced, and reduces the manual overhead of managing individual access rights.

Automated Authentication via User CRD Certificate Generation: The User CRD has been enhanced to support the automatic generation of certificates. These certificates can be used to seamlessly authenticate users, removing the need for manual certificate provisioning. This automation accelerates secure user onboarding and strengthens security by ensuring standardized authentication mechanisms are deployed automatically.

Intelligent Lifecycle Management with NiFi Version Detection: The Cloudera Flow Management Operator for Kubernetes can now automatically detect the NiFi version directly from the image tag. This eliminates the need for manual version specification, reducing human error and ensuring that the operator applies the correct configurations automatically, which simplifies operations and improves reliability.

Upgrading to the New Release:

Reference the latest operator version in the Helm Install command. More details can be found in the installation instructions. 

Helpful Links:

1. Release notes
2. Documentation

[#2]

Removed the following item as we've come to learn that the Chainguard images we were using for FIPS 140-3 compliance were in fact not compliant, even though Chainguard provide Tags to communicate that they were. 

We are investigating this on our end, but wanted to make sure the comms are up to date.

________Removed_________

FIPS 140-3 Support for NiFi 2

NiFi 2 images provided by the Cloudera Flow Management Operator for Kubernetes are now FIPS 140-3 compliant out of the box. This would apply to NiFi 2 Clusters deployed or upgraded to the latest, after upgrading to this version of the Operator.