kubesphere / kubesphere/ks-devops
Support to set image registry of Jenkins agent for improving image loading speed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 164
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
Let's assume there are four Kubernetes nodes, the Jenkins agent might be loaded in any of them. There's an image registry mirror (Nexus .e.g). So, we could support adding a config to let Jenkins load agent images from the image registry mirror (localhost:9090 .e.g.).
Users could modify a ConfigMap like this:
apiVersion: v1
data:
agent.registry.docker.io: localhost:9090
kind: ConfigMap
name: jenkins-agent-config
namespace: kubesphere-devops-system
then, the Jenkins controller will update the CasC file as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the jenkins-agent-config ConfigMap and the Jenkins controller's CasC update path, but no files or tests. Start by locating the controller code that reads this ConfigMap and updates CasC, then verify that the registry mapping is applied to agent image loading across nodes and define coverage for the requested configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100