Build Pipelines

Build pipelines let you create custom container images directly within your Kubernetes cluster — no external CI/CD required.

How Builds Work

Builds use kaniko to execute Dockerfile instructions inside a Kubernetes Job. The resulting image is pushed to your configured registry.

Source Code → kaniko Job → Docker Image → Registry → Deployment

Creating a Build

1. Navigate to Workflows → Builds
2. Click New Build
3. Configure the build:

Field	Description
Name	Build name
Dockerfile	Paste your Dockerfile content
Context	Build context (files available during build)
Destination	Registry and image tag to push to

4. Click Build

Example: Custom Jupyter Image

Build a Jupyter image with pre-installed Python packages:

FROM jupyter/scipy-notebook:latest

RUN pip install \
    langchain \
    openai \
    pandas \
    matplotlib \
    scikit-learn

USER $NB_UID

After the build completes, use the image when creating a new notebook instance.

Registry Authentication

Configure registry credentials as a Kubernetes secret:

kubectl create secret docker-registry registry-creds \
  --docker-server=your-registry.com \
  --docker-username=your-user \
  --docker-password=your-password \
  -n apps

The platform automatically mounts this secret in build jobs.

Build Logs

Monitor build progress in the build detail view. Logs stream in real time from the kaniko job output.

Build Artifacts

Successful builds push the image to your registry and record:

• Build timestamp
• Image digest (sha256)
• Build duration
• Final image size