Attach your application (preview)

This article assumes you created a Persistent Volume (PV) and a Persistent Volume Claim (PVC). For information about creating a PV, see Create a persistent volume. For information about creating a PVC, see Create a Persistent Volume Claim.

Add Cache Volumes to your aio-dp-runner-worker-0 pods

These pods are part of a statefulSet. You can't edit the statefulSet in place to add mount points. Instead, follow this procedure:

  1. Dump the statefulSet to yaml:

    kubectl get statefulset -o yaml -n azure-iot-operations aio-dp-runner-worker > stateful_worker.yaml
    
  2. Edit the statefulSet to include the new mounts for Cache Volumes in volumeMounts and volumes:

    volumeMounts: 
    - mountPath: /etc/bluefin/config 
      name: config-volume 
      readOnly: true 
    - mountPath: /var/lib/bluefin/registry 
      name: nfs-volume 
    - mountPath: /var/lib/bluefin/local 
      name: runner-local
      ### Add the next 2 lines ###
    - mountPath: /mnt/esa 
      name: esa4 
    
    volumes: 
    - configMap: 
        defaultMode: 420 
        name: file-config 
      name: config-volume 
    - name: nfs-volume 
    persistentVolumeClaim: 
      claimName: nfs-provisioner
      ### Add the next 3 lines ### 
    - name: esa4 
      persistentVolumeClaim: 
        claimName: esa4
    
  3. Delete the existing statefulSet:

    kubectl delete statefulset -n azure-iot-operations aio-dp-runner-worker
    

    This deletes all aio-dp-runner-worker-n pods. This is an outage-level event.

  4. Create a new statefulSet of aio-dp-runner-worker(s) with the Cache Volumes mounts:

    kubectl apply -f stateful_worker.yaml -n azure-iot-operations
    

    When the aio-dp-runner-worker-n pods start, they include mounts to Cache Volumes. The PVC should convey this in the state.

  5. Once you reconfigure your Data Processor workers to have access to the Cache Volumes, you must manually update the pipeline configuration to use a local path that corresponds to the mounted location of your Cache Volume on the worker PODs.

    In order to modify the pipeline, use kubectl edit pipeline <name of your pipeline>. In that pipeline, replace your output stage with the following YAML:

    output:
      batch:
        path: .payload
        time: 60s
      description: An example file output stage
      displayName: Sample File output
      filePath: '{{{instanceId}}}/{{{pipelineId}}}/{{{partitionId}}}/{{{YYYY}}}/{{{MM}}}/{{{DD}}}/{{{HH}}}/{{{mm}}}/{{{fileNumber}}}'
      format:
        type: jsonStream
      rootDirectory: /mnt/esa
      type: output/file@v1
    

Configure a Kubernetes native application

  1. To configure a generic single pod (Kubernetes native application) against the Persistent Volume Claim (PVC), create a file named configPod.yaml with the following contents:

    kind: Deployment
    apiVersion: apps/v1
    metadata:
      name: example-static
      labels:
        app: example-static
      ### Uncomment the next line and add your namespace only if you are not using the default namespace (if you are using azure-iot-operations) as specified from Line 6 of your pvc.yaml. If you are not using the default namespace, all future kubectl commands require "-n YOUR_NAMESPACE" to be added to the end of your command.
      # namespace: YOUR_NAMESPACE
    spec:
      replicas: 1
      selector:
        matchLabels:
          app: example-static
      template:
        metadata:
          labels:
            app: example-static
        spec:
          containers:
            - image: mcr.microsoft.com/cbl-mariner/base/core:2.0
              name: mariner
              command:
                - sleep
                - infinity
              volumeMounts:
                ### This name must match the 'volumes.name' attribute in the next section. ###
                - name: blob
                  ### This mountPath is where the PVC is attached to the pod's filesystem. ###
                  mountPath: "/mnt/blob"
          volumes:
            ### User-defined 'name' that's used to link the volumeMounts. This name must match 'volumeMounts.name' as specified in the previous section. ###
            - name: blob
              persistentVolumeClaim:
                ### This claimName must refer to the PVC resource 'name' as defined in the PVC config. This name must match what your PVC resource was actually named. ###
                claimName: YOUR_CLAIM_NAME_FROM_YOUR_PVC
    

    Note

    If you are using your own namespace, all future kubectl commands require -n YOUR_NAMESPACE to be appended to the command. For example, you must use kubectl get pods -n YOUR_NAMESPACE instead of the standard kubectl get pods.

  2. To apply this .yaml file, run the following command:

    kubectl apply -f "configPod.yaml"
    
  3. Use kubectl get pods to find the name of your pod. Copy this name, as you need it for the next step.

  4. Run the following command and replace POD_NAME_HERE with your copied value from the previous step:

    kubectl exec -it POD_NAME_HERE -- bash
    
  5. Change directories into the /mnt/blob mount path as specified from your configPod.yaml.

  6. As an example, to write a file, run touch file.txt.

  7. In the Azure portal, navigate to your storage account and find the container. This is the same container you specified in your pv.yaml file. When you select your container, you see file.txt populated within the container.

Next steps

After you complete these steps, begin monitoring your deployment using Azure Monitor and Kubernetes Monitoring or third-party monitoring with Prometheus and Grafana:

Third-party monitoring