GitHub Git Push Deployments

Continuous Integration and Deployment are native. Kubeletto coordinates repository webhooks, compilation steps, security scanning, and rolling releases on every branch update.

The Build Pipeline Architecture

Linking a GitHub repository sets up a multi-step compilation workspace:

1. Webhook Event Ingestion: A push to your branch (e.g. main) triggers an authenticated webhook processed by platform-core.
2. Workspace Isolation: An ephemeral build worker (platform-worker) checks out the repository commit.
3. Dockerfile Build: The worker locates your Dockerfile in the repository root and compiles it using BuildKit. A Dockerfile is required — push one to your repo before triggering a git deployment.
4. Isolation & Sandbox: The compilation runs inside an isolated build container using runc, restricted by seccomp and AppArmor profiles.
5. Storage & Registry: The completed OCI image is pushed to the integrated container registry backed by secure object storage.
6. Traffic Rollout: platform-core updates routing variables, executing a rolling update to redirect ingress HTTP requests to the new service revision.