Download skills/kubesphere-devops-overview/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does kubesphere-devops-overview live?
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Which agents can use kubesphere-devops-overview?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Use when working with KubeSphere DevOps extension, CI/CD pipelines, Jenkins integration, or pipeline troubleshooting
name: kubesphere-devops-overview
description: Use when working with KubeSphere DevOps extension, CI/CD pipelines, Jenkins integration, or pipeline troubleshooting
KubeSphere DevOps Overview
Overview
KubeSphere DevOps provides CI/CD capabilities through Jenkins integration, supporting both graphical pipeline editing and Jenkinsfile-based pipelines. It enables automated builds, testing, and deployments across multi-cluster environments with ArgoCD integration for GitOps continuous deployment.
When to Use
Setting up CI/CD pipelines in KubeSphere
Configuring Jenkins integration
Managing DevOps projects and pipelines
Troubleshooting pipeline execution issues
Integrating with GitHub, GitLab, or SVN repositories
Configuring SonarQube for code quality
Core Concepts
Resource Mapping
KubeSphere DevOps maps resources across three layers:
Key Concept: A "DevOps Project" in KubeSphere is fundamentally a Kubernetes namespace with the devops.kubesphere.io/managed=true label. The DevOpsProject CR exists as a wrapper resource, but when querying for accessible DevOps projects, you interact with namespaces, not the DevOpsProject CRs directly.
For tenants: Use the /kapis/devops.kubesphere.io/v1alpha3/workspaces/{workspace}/namespaces endpoint to list accessible DevOps projects (returns namespace resources). The /apis/devops.kubesphere.io/v1alpha3/devopsprojects endpoint requires cluster-scoped permissions and returns 403 for tenants.
DevOps Project Naming Convention
DevOps projects have two forms of names:
Name Type
Example
Source
Usage
Shortname
devopstest
.metadata.generateName in DevOpsProject CR
Display/user-friendly name
Fullname
devopstestc2nj7
.metadata.name in DevOpsProject CR and Namespace
Actual resource identifier
Important:
The fullname is the actual Kubernetes namespace name (e.g., devopstestc2nj7)
When creating a DevOps project with shortname devopstest, KubeSphere generates a unique fullname by appending random characters
All API operations use the fullname (namespace name), not the shortname
When a user refers to a project by shortname and multiple projects match, ask for confirmation before proceeding
# Check DevOps pods
kubectl get pods -n kubesphere-devops-system
# Check InstallPlan status
kubectl get installplan devops -n kubesphere-system
# For multi-cluster: check agent status on each cluster
kubectl get installplan devops -n kubesphere-system -o jsonpath='{.status.clusterSchedulingStatuses}'
Architecture
Component
Purpose
Namespace
devops-jenkins
Jenkins master
kubesphere-devops-system
devops-apiserver
DevOps API service
kubesphere-devops-system
devops-controller
Resource controllers
kubesphere-devops-system
devops-argocd-*
ArgoCD (GitOps)
argocd
Jenkins Agent
Pipeline executors
Dynamic (per pipeline)
-----------
---------
-----------
devops-jenkins
Jenkins master
kubesphere-devops-system
devops-apiserver
DevOps API service
kubesphere-devops-system
devops-controller
Resource controllers
kubesphere-devops-system
Jenkins Agent
Pipeline executors
Dynamic (per pipeline)
Jenkins Integration
KubeSphere DevOps integrates with Jenkins for CI/CD execution. The secret devops-jenkins contains the admin token for direct Jenkins access:
# Get Jenkins admin token
TOKEN=$(kubectl -n kubesphere-devops-system get secret devops-jenkins -o jsonpath='{.data.jenkins-admin-token}' | base64 -d)
# Access Jenkins API
kubectl run curl-jenkins --rm -i --restart=Never --image=curlimages/curl \
-- "http://admin:${TOKEN}@devops-jenkins.kubesphere-devops-system:80/api/json"
Jenkins NodePort:
kubectl get svc devops-jenkins -n kubesphere-devops-system
# Default: 30180
Access Jenkins Console:
URL: http://<node-ip>:30180
Username: admin
Password: Get from secret above
ArgoCD Integration
KubeSphere DevOps includes ArgoCD v2.11.7 for GitOps continuous deployment:
ArgoCD Components:
Component
Purpose
application-controller
Manages Application state
applicationset-controller
Manages ApplicationSet resources
dex-server
SSO authentication
notifications-controller
Event notifications
repo-server
Repository operations
argocd-server
API/UI server
redis
Cache layer
Access ArgoCD:
# Get ArgoCD server URL
kubectl get svc devops-agent-argocd-server -n argocd
# Get admin password
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath='{.data.password}' | base64 -d
Key Features:
Declarative GitOps deployment
Multi-source application support
Automated sync policies
SSO integration via Dex
Notification webhooks
Key Resources
Key Resources
Resource
API Version
Purpose
Pipeline
devops.kubesphere.io/v1alpha3
CI/CD pipeline definition
DevOpsProject
devops.kubesphere.io/v1alpha3
DevOps project (namespace wrapper)
Credential
v1/Secret
Repository and deployment credentials
Quick Commands
# List DevOps projects
kubectl get devopsprojects
# List pipelines in a project
kubectl get pipelines -n <devops-project-namespace>
# Get pipeline runs
kubectl get pipelineruns -n <devops-project-namespace>
# Check Jenkins status
kubectl -n kubesphere-devops-system get pods -l app=devops-jenkins
# View Jenkins logs
kubectl -n kubesphere-devops-system logs -l app=devops-jenkins
# Get Jenkins admin password
kubectl -n kubesphere-devops-system get secret devops-jenkins -o jsonpath='{.data.jenkins-admin-password}' | base64 -d
Pipeline Types
Type
Description
Use Case
Graphical
Visual pipeline editor
Simple pipelines, no code
Jenkinsfile (SCM)
Pipeline defined in repository
Version-controlled pipelines
Jenkinsfile (Inline)
Pipeline defined in KubeSphere
Quick testing
Multi-branch
Auto-discovers branches
GitFlow, feature branches
Common Mistakes
Mistake
Fix
Pipeline fails with "No agent"
Check Jenkins agent configuration
Cannot access Git repository
Verify credentials and webhook setup
kubeconfig credentials fail
Use string type instead of kubeconfigContent (v1.2+)
Download skills/kubesphere-devops-overview/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does kubesphere-devops-overview live?
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Which agents can use kubesphere-devops-overview?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.