Introducing Jenkins to the Cloud-Native world
We want to put human operational knowledge into software operators by focusing on reducing day one activities related to installing, patching and manual work within dev tooling space.
Effortless Deployment
- Single Source of truth for Jenkins and job/pipelines configuration
- Automatically managed lifecycle
- Straightforward deployment using Kubernetes’ CR or Helm Charts
- Security Hardening out of the box
- Jenkins customization via configuration-as-code yaml and job-dsl files
Easy Maintenance
- Test different configurations in safe environment
- Utilize blue-green deployment for safe upgrades in production environments
- Minimal downtime
- GitOps declarative configuration for Jenkins and jobs/pipelines
- Use separate CI/CD instances for different teams
- Store secrets and credentials as Kubernetes resources
Disaster Recovery
- Painless configuration rollbacks
- Uncomplicated way to recreate whole instance from scratch
- Good visibility (logs in kubernetes pods)
- Remote backups on s3 compatible storage
Efficient resource utilization
Auto-scaling worker pods (Jenkins Agents) based on needs.
Reproducible Jenkins Deployment
Store all of your configuration in Git repository, automatic backups will take care of the rest of the state.
Improved Security out-of-the-box
Ships with security hardening scripts already applied.
Avoid large super-instance
Easily split your large instance into smaller ones for easier maintenance.
Leverage latest technology standards
Take advantage of Kubernetes ecosystem to make your infrastructure resilient and accelerate your development cycles.
We take security very seriously
Our top priority is to deliver secure software according to the industry standards.
Privacy
Operator Service for Jenkins respects your privacy and as part of our services we do not store any customer data.
Vulnerability Reporting
We constantly monitor recent CVEs and any potential security flaws impacting our technology stack. If you have any concerns on security that could be putting customers or your business at risk, contact us [email protected]
Recommended architecture
The diagram below shows the recommended architecture for running Jenkins on Kubernetes.
You should be aware of the following aspects of the design:
- Both the Jenkins master and agent processes have a corresponding Role-Based Authorization Strategy (RBAC) model
- Kubernetes Plugin is used to scale Jenkins agents
- There is one dedicated Seed Job Agent for creating Jenkins jobs
- A backup process is running in a sidecar container
- Authn & Authz are based on GitHub OAuth
- Backup files are uploaded to external storage, such as Azure Storage Blob
- DSL Pipelines and Job Definitions are versioned in GitHub (GitOps model)
- Secure access to the Jenkins instance is provided via VPN or Bastion Host
- Lifecycle Management is handled by the Kubernetes Operator
Talk with a technical expert
Not sure which solution is the best for you? Talk to our expert. No contract, no commitment, just a conversation. Barłomiej will contact you within 24 hours.
Bartek Antoniak
Engineering Manager
We have broad experience with the Cloud Native landscape, ranging from building platforms to large-scale cloud transformations.
Our team consists of Azure and Kubernetes certified experts, who actively participate in the Jenkins community.