How jenkinsci/kubernetes-operator works
Main Components
a. Core Components:
• Kubernetes API Server (external)
• Jenkins Operator Controller
• Jenkins Custom Resource Definition (CRD)
• Jenkins Instances (managed by the operator)
• Backup System
• Webhook Server
• Configuration Management System
b. Supporting Components:
• Notification System (with providers: Slack, MS Teams, SMTP, Mailgun)
• Monitoring/Metrics (Prometheus integration)
• Authentication/Authorization (RBAC)
Component Relationships
Kubernetes API Server <--> Jenkins Operator Controller
• (watches for Jenkins CRD changes)
• > Jenkins Instances
• (creates/updates/monitors)
• > Backup System
• (manages backup/restore operations)
• > Configuration Management
• (handles CasC and seed jobs)
• > Notification System
• (sends alerts/events)
Detailed Component Breakdown
Jenkins Operator Controller:
• Base Configuration (/pkg/configuration/base)
• User Configuration (/pkg/configuration/user)
• Backup/Restore (/pkg/configuration/backuprestore)
• Groovy Script Management (/pkg/groovy)
• Client Operations (/pkg/client)
Configuration Management:
• CasC Configuration
• Seed Jobs Configuration
• Plugin Management
• Security Settings
Key Interactions to Highlight
a. Control Flow:
• Kubernetes API Server → Operator (CRD events)
• Operator → Jenkins Instances (lifecycle management)
• Operator → Backup System (scheduled backups)
• Operator → Notification System (status updates)
b. Data Flow:
• Configuration → Jenkins Instances
• Backup Data → Storage
• Metrics → Prometheus
• Events → Notification Providers
Additional Elements
Supporting features:
• Webhook handling for Jenkins
• RBAC configuration
• Service accounts
• PVC management for backups
• Health/readiness probes
Implementation Details
Directories and their purposes:
/api - API definitions
/controllers - Core controller logic
/pkg - Main implementation
/backup - Backup functionality
/config - Kubernetes configurations