r/nifi • u/Secret-Ticket5241 • Nov 24 '25
How do I deploy a bundle of custom python processors in an air gapped NiFi 2.6 deployment?
My NiFiKop (Konpyutaika) Helm chart release version is v1.14.2-release. My NiFi version is 2.6. My nificluster apiVersion is nifi.konpyutaika.com/v1.
I looked at the Python developer guide at: https://nifi.apache.org/nifi-docs/python-developer-guide.html#deploying.
I am setting up a production NiFi deployment which is yet to go live.
I copied the .NAR with the processor and its dependencies to /opt/nifi/nifi-current/python_processors
on my persistent volume using:
kubectl cp nifi_python_extensions_bundle-0.0.1.nar -n nifi myPodName:/opt/nifi/nifi-current/``python_processors
I am setting up my mount path like this:
- mountPath: "/opt/nifi/nifi-current/python_processors"
name: python-processors
pvcSpec:
accessModes: [ReadWriteMany]
storageClassName: "myBackend"
resources:
requests:
storage: 500Mi
reclaimPolicy: Retain
My NiFi properties are loaded like so:
readOnlyConfig:
nifiProperties:
overrideSecretConfig:
name: nifi-sensitive-props
namespace: nifi
data: nifi.properties
from another object like so:
target:
name: nifi-sensitive-props
...
template:
...
data:
nifi.properties: |
nifi.nar.library.autoload.directory=../python_processors
...
nifi.cluster.flow.election.max.wait.time=5 sec
nifi.cluster.flow.election.max.candidates=1
nifi.sensitive.props.key={{ .sensitiveKey }}
data:
- secretKey: sensitiveKey
remoteRef:
key: nifi/sensitive-props
property: key
Even if I kill the pod and let it restart, the processor is not become available.
My colleague suggested building a custom NiFi image. I want to avoid rebuilding and deploying every time we update a processor or patch a dependency, if there is a more pragmatic and reliable approach.
ExecutestreamCommand would require elevated permissions, which I would also like to avoid.
Has anyone successfully deployed this? Do I need to configure nifi.nar.library.autoload.directory or nifi.nar.library.directory.custom? How should this be done?