Nifi chart

A helm chart for Nifi. Includes zookeeper subchart. Ready to roll.

Installation

➜  nifi git:(master) ✗ kubectl create ns nifi
namespace/nifi created
➜  nifi git:(master) ✗ helm install nifi . --namespace=nifi
NAME: nifi
LAST DEPLOYED: Fri May 15 16:32:16 2020
NAMESPACE: nifi
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
     NOTE: It may take a few minutes for the LoadBalancer IP to be available.
           You can watch the status of by running 'kubectl get --namespace nifi svc -w nifi'
  export SERVICE_IP=$(kubectl get svc --namespace nifi nifi -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
  echo http://$SERVICE_IP:8080
  ➜  nifi git:(master) ✗ kubectl get pods -n nifi
NAME     READY   STATUS              RESTARTS   AGE
nifi-0   0/1     ContainerCreating   0          5s
zk-0     0/1     Pending             0          5s
zk-1     0/1     Pending             0          5s
zk-2     0/1     Pending             0          5s

Be prepared to wait a while - the election process in Nifi takes around 5 minutes. You'll want to see:

nifi-1 nifi 2019-09-03 08:16:51,422 INFO [main] o.a.n.c.c.node.NodeClusterCoordinator This node is now connected to the cluster. Will no longer require election of DataFlow.

With logs afterwards containing:

nifi-1 nifi 2019-09-03 08:17:09,879 INFO [Process Cluster Protocol Request-4] o.a.n.c.p.impl.SocketProtocolListener Finished processing request 538bf832-9a5d-4f53-93c6-1f35047ca1f8 (type=HEARTBEAT, length=3566 bytes) from nifi-2:8080 in 4 millis
nifi-1 nifi 2019-09-03 08:17:11,734 INFO [Process Cluster Protocol Request-5] o.a.n.c.p.impl.SocketProtocolListener Finished processing request 6d12fcd6-99e1-4b30-a78b-a70e18e9183c (type=HEARTBEAT, length=3566 bytes) from nifi-1:8080 in 3 millis
nifi-1 nifi 2019-09-03 08:17:11,735 INFO [Clustering Tasks Thread-1] o.a.n.c.c.ClusterProtocolHeartbeater Heartbeat created at 2019-09-03 08:17:11,727 and sent to nifi-1:2882 at 2019-09-03 08:17:11,735; send took 8 millis

Configuration

Set a custom zookeeper subchart connection string It is also possible to set helm install nifi . -n nifi --set="zookeeper.deploy.enabled=false" to use an existing zookeeper deployment.

Or updating the dockerimage helm install nifi . --namespace=nifi --set=zookeeper.image.repository=foo --dry-run

zookeeper:
  deploy:
    enabled: true
  nodeList: zk-0.zk-hs,zk-1.zk-hs,zk-2.zk-hs

Web UI Access

service:
  type: LoadBalancer
  # Access the web UI from http://<IP>:8080/nifi/
  port: 8080

Specifying Values

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm upgrade --install --wait my-release \
    --set zookeeper.heapSize=512 \
    .

For more information around subchart values look within vendor/zookeeper