Skip to main content
Version: v1.11.3

Node

Node defines the nifi node basic configuration

    - id: 0
# nodeConfigGroup can be used to ease the node configuration, if set only the id is required
nodeConfigGroup: "default_group"
# readOnlyConfig can be used to pass Nifi node config
# which has type read-only these config changes will trigger rolling upgrade
readOnlyConfig:
nifiProperties:
overrideConfigs: |
nifi.ui.banner.text=NiFiKop - Node 0
# node configuration
# nodeConfig:
- id: 2
# readOnlyConfig can be used to pass Nifi node config
# which has type read-only these config changes will trigger rolling upgrade
readOnlyConfig:
overrideConfigs: |
nifi.ui.banner.text=NiFiKop - Node 2
# node configuration
nodeConfig:
resourcesRequirements:
limits:
cpu: "2"
memory: 3Gi
requests:
cpu: "1"
memory: 1Gi
storageConfigs:
# Name of the storage config, used to name PV to reuse into sidecars for example.
- name: provenance-repository
# Path where the volume will be mount into the main nifi container inside the pod.
mountPath: "/opt/nifi/provenance_repository"
# Metadata to attach to the PVC that gets created
metadata:
labels:
my-label: my-value
annotations:
my-annotation: my-value
# Kubernetes PVC spec
# https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/#create-a-persistentvolumeclaim
pvcSpec:
accessModes:
- ReadWriteOnce
storageClassName: "standard"
resources:
requests:
storage: 8Gi

Node

FieldTypeDescriptionRequiredDefault
idint32unique Node id.Yes-
nodeConfigGroupstringcan be used to ease the node configuration, if set only the id is requiredNo""
readOnlyConfigReadOnlyConfigreadOnlyConfig can be used to pass Nifi node config which has type read-only these config changes will trigger rolling upgrade.Nonil
nodeConfigNodeConfignode configuration.Nonil