### Example Node Configurations

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v0.14.0/5_references/1_nifi_cluster/4_node.md

Demonstrates how to configure multiple NiFi nodes with different settings, including using node configuration groups and specifying read-only overrides and resource requirements.

```yaml
- 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"
            # 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

```

--------------------------------

### Install Dependencies and Add Start Script

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v0.15.0/7_upgrade_guides/1_v0.7.x_to_v0.8.0.md

Install necessary npm packages and configure the start script in package.json to run the migration script.

```bash
npm init -y
npm install @kubernetes/client-node@0.16.3 minimist@1.2.6
```

```json
"start": "node --no-warnings index.js"
```

--------------------------------

### Install Helm Chart with Custom Parameters

Source: https://github.com/konpyutaika/nifikop/blob/master/helm/nifikop/README.md

Install or upgrade the Nifikop Helm chart, overriding default parameters using the --set flag. This example demonstrates setting the image tag.

```bash
$ helm install nifikop konpyutaika-incubator/nifikop --replace --set image.tag=asyncronous
```

--------------------------------

### Install NiFiKop Helm Chart

Source: https://github.com/konpyutaika/nifikop/blob/master/site/docs/6_contributing/1_developer_guide.md

Install the NiFiKop Helm chart using a locally built image. Ensure 'image.tag' matches the pushed image tag.

```bash
helm install skeleton ./helm/nifikop \
    --set image.tag=v0.5.1-release \
    --namespace-{"nifikop"}
```

--------------------------------

### Install Zookeeper with Helm

Source: https://github.com/konpyutaika/nifikop/blob/master/site/docs/3_manage_nifi/1_manage_clusters/1_deploy_cluster/1_quick_start.md

Install Zookeeper using the Bitnami Helm chart. Customize resource requests/limits, storage class, network policy, and replica count. Remember to replace `standard` with your actual storage class.

```bash
helm install zookeeper oci://registry-1.docker.io/bitnamicharts/zookeeper \
    --namespace=zookeeper \
    --set resources.requests.memory=256Mi \
    --set resources.requests.cpu=250m \
    --set resources.limits.memory=256Mi \
    --set resources.limits.cpu=250m \
    --set global.storageClass=standard \
    --set networkPolicy.enabled=true \
    --set replicaCount=3 \
    --create-namespace
```

--------------------------------

### NiFi Node Basic Configuration Example

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v1.1.0/5_references/1_nifi_cluster/4_node.md

Defines a NiFi node with a specific ID and utilizes a node configuration group for simplified setup. It also includes an example of read-only configuration to set the UI banner text, which triggers a rolling upgrade upon change.

```yaml
- 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:
```

--------------------------------

### Install cert-manager Directly

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v1.15.0/2_deploy_nifikop/1_quick_start.md

Install cert-manager by applying its YAML manifest directly. This method is suitable for straightforward installations.

```bash
# Install the CustomResourceDefinitions and cert-manager itself
kubectl apply -f \
    https://github.com/jetstack/cert-manager/releases/download/v1.17.2/cert-manager.yaml
```

--------------------------------

### Helm Install with Parameters

Source: https://github.com/konpyutaika/nifikop/blob/master/site/docs/2_deploy_nifikop/2_customizable_install_with_helm.md

Install the Nifikop Helm chart and set specific parameters, such as the target namespaces. This command deploys the chart with the specified configuration.

```bash
helm install nifikop konpyutaika/nifikop --set namespaces={"nifikop"}
```

--------------------------------

### Install cert-manager Directly

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v1.12.0/2_deploy_nifikop/1_quick_start.md

Install the CustomResourceDefinitions and cert-manager directly using kubectl. This method is suitable for straightforward installations.

```bash
kubectl apply -f 
    https://github.com/jetstack/cert-manager/releases/download/v1.7.2/cert-manager.yaml
```

--------------------------------

### Install Zookeeper using Helm

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v0.11.0/2_setup/1_getting_started.md

Installs Zookeeper using the Bitnami Helm chart. Ensure to replace 'standard' with your actual storage class if needed.

```bash
helm install zookeeper bitnami/zookeeper \
    --namespace=zookeeper \
    --set resources.requests.memory=256Mi \
    --set resources.requests.cpu=250m \
    --set resources.limits.memory=256Mi \
    --set resources.limits.cpu=250m \
    --set global.storageClass=standard \
    --set networkPolicy.enabled=true \
    --set replicaCount=3 \
    --create-namespace
```

--------------------------------

### NiFi Node Basic Configuration Example

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v1.11.3/5_references/1_nifi_cluster/4_node.md

Illustrates the configuration of two NiFi nodes, one using a default configuration group and the other with specific resource limits and storage configurations.

```yaml
- 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

```

--------------------------------

### Install cert-manager Directly

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v0.14.1/2_deploy_nifikop/1_quick_start.md

Install the CustomResourceDefinitions and cert-manager directly using kubectl. This method is suitable for straightforward installations.

```bash
kubectl apply -f \
    https://github.com/jetstack/cert-manager/releases/download/v1.7.2/cert-manager.yaml
```

--------------------------------

### Install cert-manager Directly

Source: https://github.com/konpyutaika/nifikop/blob/master/site/docs/2_deploy_nifikop/1_quick_start.md

Install cert-manager and its CustomResourceDefinitions directly from the release URL. This method is suitable for straightforward installations.

```bash
kubectl apply -f \
    https://github.com/jetstack/cert-manager/releases/download/v1.17.2/cert-manager.yaml
```

--------------------------------

### Install Zookeeper with Helm

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v1.11.2/3_manage_nifi/1_manage_clusters/1_deploy_cluster/1_quick_start.md

Installs a Zookeeper cluster using the Bitnami Helm chart. Ensure to replace the `global.storageClass` with your specific storage class.

```bash
helm install zookeeper oci://registry-1.docker.docker.io/bitnamicharts/zookeeper \
    --namespace=zookeeper \
    --set resources.requests.memory=256Mi \
    --set resources.requests.cpu=250m \
    --set resources.limits.memory=256Mi \
    --set resources.limits.cpu=250m \
    --set global.storageClass=standard \
    --set networkPolicy.enabled=true \
    --set replicaCount=3 \
    --create-namespace
```

--------------------------------

### Install Dependencies for CRD Migration

Source: https://github.com/konpyutaika/nifikop/blob/master/site/docs/7_upgrade_guides/1_v0.7.x_to_v0.8.0.md

Install the necessary Node.js packages for the CRD migration script. Ensure you have Node.js and npm installed.

```bash
npm init -y
npm install @kubernetes/client-node@0.16.3 minimist@1.2.6
```

--------------------------------

### Deploy NiFiKop Helm Chart with Resource Settings

Source: https://github.com/konpyutaika/nifikop/blob/master/site/website/versioned_docs/version-v1.14.2/2_deploy_nifikop/1_quick_start.md

Install the NiFiKop Helm chart with specified image tag, resource requests, limits, and target namespaces. Ensure the namespace exists before running.

```bash
helm install nifikop \
    oci://ghcr.io/konpyutaika/helm-charts/nifikop \
    --namespace=nifi \
    --version 1.14.2 \
    --set image.tag=v1.14.2-release \
    --set resources.requests.memory=256Mi \
    --set resources.requests.cpu=250m \
    --set resources.limits.memory=256Mi \
    --set resources.limits.cpu=250m \
    --set namespaces={"nifi"}
```