Jenkins · Kubernetes · Operations

One controller.
Agents on demand.

A deployment in Azure East Asia verified that the controller coordinates while ephemeral Kubernetes pods execute the work.

这是 Walker Kubernetes 生产学习路径中的真实工程案例。

从生产知识整理，到故障场景训练，再到可运行的平台工程。

Walker 的 Kubernetes 生产工程实践：以证据链完成架构设计、部署验证、故障诊断与可逆运维。

Open Jenkins ↗查看完整案例 View runbook

动态 Pod Agent 已创建、执行并回收。以上是 2026-08-06 的一次部署验证，不是实时监控、持续在线或 SLA 承诺；为节省云额度，Jenkins 可能暂停运行。

No Jenkins credentials are stored in this portal.

01 / Platform

Designed for a small blast radius.

Controller

Jenkins 2.555.3 LTS · Java 21

Persistent, zero executors

Kubernetes

1.36 baseline

Namespace-scoped RBAC

Network

Ingress + managed TLS

Public HTTPS endpoint

Storage

20 Gi RWO PVC

Snapshot before upgrades

02 / Agents

Every build gets a clean room.

BASEdefault

base

Scripts, tests and lightweight builds in a restricted pod. Created per job and removed at completion.

Tools: Alpine utility container
Service account: jenkins-agent
Retention: Never

BUILDunprivileged

container-build

OCI image builds with Kaniko. No privileged mode, host path or Docker socket required.

Builder: Kaniko 1.23.2
Service account: jenkins-agent
Instance cap: 5 pods

03 / Runbook

Operate deliberately.

Deploy

Create the admin Secret, validate manifests, then run the atomic Helm release.

Verify

Check rollout, HTTPS, PVC, RBAC, then run the sample dynamic-agent Pipeline.

Upgrade

Snapshot first. Review LTS, chart and plugin changes before updating pinned versions.

Rollback

Restore the Helm revision; restore the matching PVC snapshot if data changed.

One controller.Agents on demand.