Building Docker Images

ReleaseHub allows you to build Docker images for your Helm charts. You can define any number Docker builds for your application. The Dockerfiles must exist in the application's source control repository. You can not specify Docker builds from remote source control repositories.
builds:
- name: nginx
  dockerfile: Dockerfile
  context: nginx
  args:
  - MAX_UPLOAD_SIZE=60
- name: backend
  dockerfile: Dockerfile-backend
  context: app
Example Docker builds for a custom ngnix and backend containers
Build Environment Variables
Each container built by ReleaseHub will generate environment variables that can be used in your Helm charts. By default ReleaseHub adds environment variables for the Docker registry and path to the image built.
- key: RELEASE_REGISTRY_ENDPOINT
  value: 123456789000.dkr.ecr.us-east-1.amazonaws.com
  secret: false
- key: RELEASE_REGISTRY_PATH
  value: 123456789000.dkr.ecr.us-east-1.amazonaws.com/acme-org/acme-app
  secret: false
Each container build will generate environment variables that can be used in your Helm charts. Two environment variables are emitted per build. The ngnix build shown in the first example will generate NGINX_REGISTRY_IMAGE_URLandNGINX_REGISTRY_IMAGE_SHA
- key: NGINX_REGISTRY_IMAGE_URL
  value: 123456789000.dkr.ecr.us-east-1.amazonaws.com/acme-org/acme-app/[email protected]:f1e8b983e8f842170caed5ce76fa92171acfc0f8296283c85155771374adec9c
  secret: false
- key: NGINX_REGISTRY_IMAGE_SHA
  value: f1e8b983e8f842170caed5ce76fa92171acfc0f8296283c85155771374adec9c
- key: BACKEND_REGISTRY_IMAGE_URL
  value: 123456789000.dkr.ecr.us-east-1.amazonaws.com/acme-org/acme-app/[email protected]:4852bafb7f7cf76375d0e090f737926210de462ef35c9f9616f8a2e17ebb0dda
  secret: false
- key: BACKEND_REGISTRY_IMAGE_SHA
  value: 4852bafb7f7cf76375d0e090f737926210de462ef35c9f9616f8a2e17ebb0dda
  secret: false
Example of generated build environment variables.

Open Source Charts

Ingress and Networking

Last modified 8d ago

Copy link