v1

Secure /

Upload secret files

You can upload secret files to mount within your containers. They can be used to:

  • make configuration files available within your services, jobs and builds
  • create text based configuration files like .json, .html, .css, .yaml
  • add certificate files or complex secrets that cannot be handled by environment variables
  • create manifest files with build or runtime variable configuration

Secret files are equivalent to Kubernetes' ConfigMaps and Docker file volumes .

Each secret file must have a unique path where it will be mounted, and some file content. You can use dynamic templating (in the format ${ENV_KEY}) to substitute environment variables into your secret files.

Secret files are encrypted at rest and injected at runtime as environment variables, or build time as build arguments.

Add a secret file

You can add a secret file to a service or job from the environment or build arguments pages, to add a file to be available at runtime or build respectively.

Click add file to manually enter the file content, or upload from your local filesystem. Enter the mount path, where your file will be located in the container filesystem, and either repeat to add more files or save changes.

You can also add secret files in the same way to a secret group, which will be made available in any services or jobs that inherit from that secret group.

Edit a secret file

You can edit or delete existing secret files by finding them in the relevant service, job, or secret group.

© 2022 Northflank Ltd. All rights reserved.