Volume distribution

Microservices often need files on the Edgelet node before a container starts. With iofogctl, you push directories from your operator machine to selected nodes using the Volume kind.

This is orchestrator-driven file distribution. It is separate from:

• VolumeMount (ConfigMap/Secret materialization) - see Volume mounts in Learn
• On-node VOLUME mappings - see Edgelet volumes

Volume YAML

---
apiVersion: iofog.org/v3
kind: Volume
spec:
  name: secret
  source: /tmp/
  destination: /tmp/secrets/
  permissions: 666
  agents:
    - zebra-1
    - zebra-2

Deploy:

iofogctl deploy -f volume.yaml

With the example above, everything under /tmp/ on your operator machine is pushed to /tmp/secrets/ on zebra-1 and zebra-2.

Use in microservices

After the Volume is deployed, reference the destination path in microservice volume mappings. See Applications in Learn for mount syntax.

List, describe, and delete Volumes like any other iofogctl resource:

iofogctl get volumes
iofogctl describe volume secret
iofogctl delete volume secret

See also

• Volume kind - YAML overview
• Edgelet volumes - VOLUME, BIND, and prune behavior on the node
• Microservice registry and catalog

See anything wrong with the document? Help us improve it!

Edit this page on GitHub!