Jenkins K8s
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 201 | 29 Sep 2025 | |
| latest/stable | 200 | 29 Sep 2025 | |
| latest/edge | 237 | 28 Nov 2025 | |
| latest/edge | 236 | 28 Nov 2025 |
juju deploy jenkins-k8s
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
How to integrate with machine agents
Prerequisites
This guide assumes the jenkins-k8s charm to already be deployed on a k8s juju model tutorial.
To integrate machine (VM) agents, you’ll need to have a bootstrapped machine model. Learn about bootstrapping different clouds here.
Use juju bootstrap localhost localhost to bootstrap a lxd machine controller with the name
localhost for tutorial purposes.
Use juju add-model tutorial to add a model named tutorial.
Deploy Jenkins agents (VM)
Deploy 3 units of jenkins agents on the lxd cloud.
# Deploy an edge version of the charm until stable version is released.
juju deploy jenkins-agent --channel=latest/edge -n3
Create an offer for cross model relation
To relate charms
across different models, a Juju
offer is
required.
Create an offer of the jenkins-agent charm’s agent relation.
juju offer jenkins-agent:agent
The output should look similar to the contents below:
Application "jenkins-agent" endpoints [agent] available at "admin/tutorial.jenkins-agent"
Relate Jenkins agents through the offer
Switch back to the k8s model where jenkins-k8s charm is deployed. An example of the switch
command looks like the following: juju switch microk8s-localhost:tutorial.
Relate the agents to the jenkins-k8s server charm through the offer.
The syntax of the offer is as follows: <controller>:<user>/<model>.<charm>.
juju relate jenkins-k8s:agent localhost:admin/tutorial.jenkins-agent