Running Jenkins In Kubernetes - Tutorial And Review
Video Statistics and Information
No captions available for this video.
Channel: DevOps Toolkit
Views: 5,219
Rating: undefined out of 5
Keywords: jenkins kubernetes, jenkins, ci, cd, ci/cd, pipelines, jenkins kubernetes pipeline, jenkins kubernetes plugin, jenkins kubernetes deployment, jenkins kubernetes continuous deploy plugin, jenkins kubernetes plugin configuration, jenkins kubernetes ci cd, jenkins kubernetes pipeline example, jenkins kubernetes agent, devops, devops toolkit, review, viktor farcic, jenkins kubernetes integration, jenkins tutorial, jenkins pipeline, jenkins ci cd pipeline, ci/cd pipeline, ci/cd tutorial
Id: 2Kc3fUJANAc
Channel Id: undefined
Length: 32min 33sec (1953 seconds)
Published: Thu May 20 2021
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
I’ll respond as if this is a question being asked vs a reason to click the link.
Jenkins is a old workhorse that can work in 2021, but that doesn’t mean you should keep using it. If it was me in 2021 I would look at other lighter more agile systems options. If you want to self host look at things like Argo and tectonic. If you want a nice system that is hosted for you look at things like buildkite, github actions, circle ci.
I was posed with the exact question when I had to implement a CI/CD pipeline ground up. I decided to go ahead with GitHub actions + self hosted runners. Not having to manage an elephant is a bliss. However it might not be the best solution for you though worth evaluating.
If grown to prefer right tool for the job instead of tool that does all jobs.
The tool you know how works and fails is the correct tool for the job
Jenkins is old and most failures are known. Always find the tool that you know how it breaks then see if it works
unless you arent worried about production... then go play with whatever :)
Tekton and Flux v2 ftw
No, if you can avoid it.
Jenkins is still relevant. I'm using it with:
Works great and has a tonne of plugins for build reports/actions.
edit: Also using nginx-ingress with oauth2_proxy and
enable-global-auth: true, and https://plugins.jenkins.io/reverse-proxy-auth-plugin/ for automatic login from auth headerJenkins remains the swiss army knife for pipelines. If you need to build a complex pipeline with multiple technologies integrated (particularly where some may not be known/fully understood at the beginning)--Jenkins offers range and flexibility that you can be confident the pipeline can be expanded as required.
That said, if you need a knife then you don't get a swiss army knife. Refer to Crocodile Dundee for details.
For the people who say no how complex is your pipeline. In other words how many stages do you run? We have 65+ stages that can be created on the fly, Is there a python based solution that works onprem and in the cloud and supports some form of configuration as code? Please say it's so....