Cloud-Native Kubernetes-First Serverless Continuous Delivery With Jenkins X, Kubernetes, And Friends
A lot changed since we were introduced to cloud, Kubernetes, and containers. Whatever we did in the past might not be valid anymore. Our applications need to become cloud-native, we need to adopt Kubernetes as the first class citizen, and there is no doubt anymore that continuous delivery is a must for any company that wants to stay competitive. The problem is that Kubernetes is complicated and the ecosystem is vast. Understanding low-level details takes more time than we might have, and yet we need to get everyone on board. We need a tool that will allow us to leverage all the latest and greatest processes and tools. At the same time, we need them to be simple and straightforward so that everyone can benefit from them. That is the primary objective behind the Jenkins X project. It brings power by combining best practices and tools while keeping it so simple that anyone can use it.
Jenkins X, an open source project introduced to the community by CloudBees, enables the rapid creation, delivery and orchestration of cloud-native applications based on continuous delivery best practices and the proven Kubernetes platform.
By combining the power of Jenkins, its community and the power of Kubernetes, the Jenkins X project provides a path to the future of continuous delivery for microservices and cloud-native applications.
Jenkins X is Jenkins and additional best of breed tools and software for Kubernetes. It provides an interactive command-line interface to instantiate applications, repositories, environments, and pipelines and orchestrate continuous integration and continuous delivery.
It is the CI/CD solution for development of modern cloud applications on Kubernetes.
We’ll explore how to create a fully operational continuous delivery pipeline using containers, Kubernetes, Jenkins X, and quite a few other tools.
General requirements for the workshop are as follows:
GitBash (if using Windows)
You can choose to have a cluster in you own Google (GKE), Amazon (EKS), or Azure (AKS) account, or you can use one that will be available to you during the workshop.
If you choose to use your own account, please follow the instructions for the cloud-specific requirements. If you’re in doubt which one to choose, I strongly recommend GKE. If you register, you’ll get 300$ in free credit and we won’t spend more than a few $ during the workshop. On the other hand, if you do choose to use the cluster that will be available (and prepared by me) during the workshop, there is nothing else you need to do in advance.
Check out the additional requirements here: https://github.com/vfarcic/vfarcic.github.io/blob/master/jx/abstracts/REQS.md