Skip to main content

Buildpacks

info

Buildpacks have nothing in common with buildpacks.io. Your Code will not be built into the running image but mounted read-only into the running image.

Kubero buildpack-images rely on public available images.

Examples of Kubero Buildpacks can be found here: https://github.com/kubero-dev/buildpacks/tree/main/packs

Buildpacks are defined as a set of three containers:

Fetch (init container)​

Fetches the code from a Git repository. There is a working fetch container from kubero. But if you wish to build your own, you are free to change it in the buildpack configuration.

Build (init container)​

Runs the build commands. You can define which image will be used by selecting the buildpack. The buildpack can be configured with any Docker image.

Run (container)​

Run the final container In the run stage, there are two options: worker and web. Only the web pod is attached to the ingress and will be accessible from outside the cluster.

Example for a buildpack configuration:​

  - name: Python
    language: Python
    fetch:
      repository: ghcr.io/kubero-dev/buildpacks/fetch
      tag: main
    build:
      repository: python
      tag: 3.10-buster
      command: "python3 -m venv .venv && . .venv/bin/activate && pip install -r requirements.txt"
    run:
      repository: python
      tag: 3.10-buster
      command: "python3 -m venv .venv && . .venv/bin/activate && python3 main.py"

This config is stored in your Kubernetes cluster and can be changed by kubectl.

kubectl edit kuberoes kubero -n kubero