Michael H

I discovered through working on this that most of the metrics in the linked Prometheus example are already provided by the controller runtime. There may still be additional metrics we'd...

Off the top of my head, we could capture metrics around the following: - Number, response code, and duration of requests-by-API-endpoint to NiFi nodes/clusters - Number of CRDs a nifikop...

I think this sort of change ought to warrant a major version update in nifikop (i.e. nifikop v2.0.0). What do you think? then the guidance can be: - Use nifikop...

This is an interesting idea, but I hesitate to make it a custom resource given the number of ways & places nars can be hosted. Nars could be hosted via...

Another thing to consider is that NiFi will eventually support pulling extensions (nars) via NiFi Registry: https://nifi.apache.org/docs/nifi-registry-docs/html/administration-guide.html#bundle-persistence-providers Stateless NiFi already behaves this way: https://github.com/apache/nifi/blob/main/nifi-stateless/nifi-stateless-assembly/README.md > When Stateless NiFi is started,...

> I analyzed your suggestion and I understood that NiFi registry is an subproject that should be installed "additionally" to NiFi. Does this operator support also the registry installation? Nifikop...

Okay, so this is all declarative configuration for a deployment. If you want a new nar in your deployment, you need to add it to an init container. Deployed pods...

> sorry I'm not sure we are 100% aligned. Each NiFi pod has its own volume attached (as it is now without change). In this volume there is a folder...

This would require a change in ArgoCD or a custom application health Lua snippet for the NiFi pods: https://argo-cd.readthedocs.io/en/stable/operator-manual/health/

I believe these would all need exposed in the `nifi-cluster` helm chart as we do with the logback configuration. Except in these cases, i don't think we need to provide...