Jenkins On Kubernetes 

We all want to be High Performing Teams ! 

Development teams need to figure out : ● How to do microservices well ? ● How to do Kubernetes well ? ● How to do cloud well ? ● How to automate CI / CD ? ● A LOT OF STUFF ! 

Introducing Jenkins X 

Jenkins X ● Built on Jenkins foundations, recharges it — doesn’t replace it. ● Rethinks how developers should interact with CI/CD in the cloud through automation, tooling and DevOps best practices. ● Understands clouds and Kubernetes natively. You no longer need to play around with Kubernetes setup in Jenkinsfile ● Build for modern cloud with modern development practices 

How does Jenkins X help ? ● Automates the setup : tools + environment ○ Jenkins, nexus, helm, skaffold ● Automates CI/CD for your applications on Kubernetes ○ Docker Images ○ Helm charts ○ Pipelines 

● Use GitOps to manage promotion between environments ○ Test -> Staging -> Production ○ Configuration stored in Git ● Lots of Feedback ○ E.g commenting on issue as they hit staging + Production 

What does Jenkins X give me? ● Development Tools Environment ○ Jenkins master ○ Elastic pool of Kubernetes build pods ● Staging Environment ● Production Environment ● CI/CD configured out of the box 

How can we use Jenkins X? ● With existing cluster: ○ jx boot ● With a Jenkins X managed kubernetes cluster: ○ jx create cluster gke --skip-login ● You can use any Kubernetes provider such as AWS EKS, OpenShift, or your own handmade cluster. 

Using Jenkins X for Projects ● Import existing projects using ○ jx import ○ Creates a Dockerfile, Jenkinsfile, Helm charts and configures build packs for deployment ● Create new projects with ○ jx create quickstart 

● This will setup a new project with Jenkins X configured. Changes will automatically go into the staging environment ● Once you are happy, promote the build to production ○ jx promote ● Comment on PRs, merging will finalize the deployment! ● Profit! 

Advanced Strategies ● GitOps ● Canary deployments ● Staged rollouts ● Blue Green deployments 

Comparing Traditional CI/CD to Jenkins X Jenkins ● Holistic, makes no assumption on what's running ● Familiar ● Straightforward Jenkins X ● Opinionated. Brings a host of baggage ● Paradigm shift. Needs you to rethink what you do with your project; configure build-packs etc 

Thank You