Introduction

Kubero is our internal CI/CD platform for building and deploying containerized applications on Kubernetes. It manages the full lifecycle — from GitLab push to running pods — through a chain of admission webhooks, custom build images, and automated triggers.

What You Get

• GitLab-triggered builds — Push code, get a running app
• Zero-config CI — Dockerfile-based builds with automatic registry push
• Admission webhook pipeline — Injects credentials, rewrites images, fixes buildah issues
• Multi-environment support — Stage, production, and review environments

How It Works

GitLab push → Trigger Service → Kubero API → Build Job
                                      ↓
                              Admission Webhook
                                      ↓
                              fetch → push → deploy

Key Components

Component	Purpose
Kubero Server	Dashboard, API, app management
Kubero Operator	Creates build Jobs, manages deployments
GitLab Trigger	Receives webhooks, triggers builds
Admission Webhook	Mutates Jobs (PAT injection, image rewrite)
Custom Fetch	Git clone with PAT authentication
Custom Buildah	Builds images with short-name fix

Prerequisites

• Kubernetes cluster v1.30+
• Docker registry (registry.ks.vaah.ai)
• GitLab instance (git6.webreinvent.com)
• kubectl access with admin privileges