Skip to content

Workload files

Ankaios supports mapping files to workloads. The user can define files in the files field of a workload configuration, which supports text and base64 encoded content. The files are mounted in readonly mode. Workload files are not supported for a workload with runtime podman-kube. Instead, use the built-in ConfigMaps feature of podman-kube.

The following manifest contains a workload with a mounted web server configuration and another workload which outputs the content of a mounted base64 encoded file to the terminal. It also combines the config object approach with workload files by defining the configuration separated from the workload. Ankaios expands the templated subfields data and binaryData using the handlebars template engine.

To get an overview about which workload configuration fields currently support template expansion, see here.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
apiVersion: v0.1
workloads:
  nginx:
    agent: agent_A
    runtime: podman
    configs:
      nginx_conf: nginx_config
    files:
      - mountPoint: "/etc/nginx/nginx.conf" # mount point in the container
        data: "{{nginx_conf}}" # (1)!
    runtimeConfig: |
      image: docker.io/nginx:latest
      commandOptions: [ "-p", "8087:80" ]
  hello:
    agent: agent_A
    runtime: podman
    configs:
      bin_data: bin_data
    files:
      - mountPoint: "/hello" # mount point in the container
        binaryData: "{{bin_data}}" # (2)!
    runtimeConfig: |
      image: docker.io/alpine:latest
      commandOptions: [ "--entrypoint", "/bin/sh" ]
      commandArgs: [ "-c", "cat /hello" ]
configs:
  nginx_config: |
    worker_processes  1;

    events {
        worker_connections  1024;
    }

    http {
        server {
            listen 80;
            server_name custom_nginx;

            location /custom {
                default_type text/plain;
                return 200 "The mounted custom nginx.conf is being used!\n";
            }
        }
    }
  # base64 encoded content
  bin_data: SGVsbG8sIFdvcmxkIQ==

  1. The contents of the data field will be expanded and replaced with the custom web server configuration of nginx_config part of the configs field below.

  2. The contents of the binaryData field will be expanded and replaced with the content of bin_data part of the configs field below.

Note

Ankaios expects base64 data in the Standard Base64 Encoding including padding according to RFC 4648. Example: echo -n "Hello, World!" | base64. Ankaios decodes the base64 data before mounting the file to the workload.