How to deploy Apache Nifi Statefulset in cluster mode with external zookeeper? - kubernetes

Question

I tried to deploy Apache Nifi (statefulset) in Kubernetes, in cluster mode. Firstyly I am trying only one node but I don't know where I am wrong in the yaml and how to access the Nifi UI when I deploy Nifi statefulset. I use external zookeeper.
Not sure if I have to create service for each node of the cluster.
On K8S dashboard nifi pod is working well.
I know that Stateful sets allow the creation of stable network identities of pods by creating what is known as a headless service. But how can I access the UI next ?
Nifi StatefulSet yaml file:
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: nifi
labels:
name: nifi
app: nifi
annotations:
app.kubernetes.io/name: nifi
app.kubernetes.io/part-of: nifi
spec:
serviceName: nifi
# replicas: 2
revisionHistoryLimit: 1
# strategy:
# type: Recreate
selector:
matchLabels:
app: nifi
template:
metadata:
labels:
app: nifi
spec:
automountServiceAccountToken: false
enableServiceLinks: false
restartPolicy: Always
securityContext:
runAsGroup: 1000
runAsUser: 1000
runAsNonRoot: true
seccompProfile:
type: RuntimeDefault
containers:
- name: nifi
image: XXX
imagePullPolicy: IfNotPresent
ports:
- containerPort: 8080
name: nifi
- containerPort: 8082
name: cluster
env:
- name: "NIFI_SENSITIVE_PROPS_KEY"
value: "nificlusterbulot"
- name: NIFI_WEB_HTTP_HOST
value: "nifi-0.NAMESPACE_NAME.svc.cluster.local"
- name: NIFI_WEB_HTTP_PORT
value: "8080"
- name: NIFI_ANALYTICS_PREDICT_ENABLED
value: "true"
- name: NIFI_ELECTION_MAX_CANDIDATES
value: "2"
- name: NIFI_ELECTION_MAX_WAIT
value: "1 min"
- name: NIFI_CLUSTER_IS_NODE
value: "true"
- name: NIFI_JVM_HEAP_INIT
value: "3g"
- name: NIFI_JVM_HEAP_MAX
value: "4g"
- name: NIFI_CLUSTER_NODE_CONNECTION_TIMEOUT
value: "2 min"
- name: NIFI_CLUSTER_PROTOCOL_CONNECTION_HANDSHAKE_TIMEOUT
value: "2 min"
- name: NIFI_CLUSTER_NODE_PROTOCOL_MAX_THREADS
value: "15"
- name: NIFI_CLUSTER_NODE_PROTOCOL_PORT
value: "8082"
- name: NIFI_CLUSTER_NODE_READ_TIMEOUT
value: "15"
- name: NIFI_ZK_CONNECT_STRING
value: "zookeeper:2181"
- name: NIFI_CLUSTER_NODE_ADDRESS
value: "nifi-0.nifi.NAMESPACE_NAME.cluster.local"
# valueFrom:
# fieldRef:
# fieldPath: status.podIP
# - name: HOSTNAME
# valueFrom:
# fieldRef:
# fieldPath: status.podIP
livenessProbe:
exec:
command:
- pgrep
- java
initialDelaySeconds: 60
periodSeconds: 30
timeoutSeconds: 10
failureThreshold: 3
successThreshold: 1
readinessProbe:
exec:
command:
- pgrep
- java
initialDelaySeconds: 180
periodSeconds: 30
timeoutSeconds: 10
failureThreshold: 3
successThreshold: 1
resources:
requests:
cpu: 400m
memory: 1Gi
limits:
cpu: 500m
memory: 2Gi
volumes:
- name: pv-01
persistentVolumeClaim:
claimName: pv-claim
Zookeeper yaml file:
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: zookeeper
namespace: namespace_name
labels:
name : zookeeper
app : zookeeper
# annotations:
# app.kubernetes.io/name: zookeeper
# app.kubernetes.io/part-of: nifi
spec:
revisionHistoryLimit: 1
serviceName: zookeeper
selector:
matchLabels:
app: zookeeper
template:
metadata:
labels:
app: zookeeper
spec:
automountServiceAccountToken: false
enableServiceLinks: false
restartPolicy: Always
securityContext:
runAsGroup: 1000
runAsUser: 1000
runAsNonRoot: true
seccompProfile:
type: RuntimeDefault
containers:
- name: zookeeper
image: XXX
imagePullPolicy: IfNotPresent
ports:
- containerPort: 2181
name: zk
- containerPort: 2182
name: zc
# - containerPort: 8083
# name: web
- containerPort: 5111
name: cmd
env:
- name: ALLOW_ANONYMOUS_LOGIN
value: "yes"
- name: ZOO_ADMINSERVER_ENABLED
value: "true"
- name: ZOO_AUTOPURGE_PURGEINTERVAL
value: "2"
- name: ZOO_AUTOPURGE_SNAPRETAINCOUNT
value: "10"
- name: ZOO_INIT_LIMIT
value: "10"
- name: ZOO_STANDALONE_ENABLED
value: "true"
- name: ZOO_SYNC_LIMIT
value: "6"
- name: ZOO_TICK_TIME
value: "4000"
livenessProbe:
exec:
command:
- which
- java
initialDelaySeconds: 30
periodSeconds: 30
timeoutSeconds: 10
failureThreshold: 3
successThreshold: 1
readinessProbe:
tcpSocket:
port: 2181
initialDelaySeconds: 120
periodSeconds: 30
timeoutSeconds: 10
failureThreshold: 3
successThreshold: 1
resources:
requests:
cpu: 200m
memory: 1Gi
limits:
cpu: 300m
memory: 2Gi
securityContext:
allowPrivilegeEscalation: false
privileged: false
runAsGroup: 1000
runAsUser: 1000
- name: pv-01
persistentVolumeClaim:
claimName: pv-claim