DevOps Pro Moscow 2019

Viktor Farcic

CloudBees, Spain

BIO

Viktor Farcic is a Developer Advocate at CloudBees, a member of the Docker Captains group, and published author.
He coded using a plethora of languages starting with Pascal (yes, he is old), Basic (before it got Visual prefix), ASP (before it got .Net suffix), C, C++, Perl, Python, ASP.Net, Visual Basic, C#, JavaScript, Java, Scala, etc. He never worked with Fortran. His current favorite is Go.
His big passions are DevOps, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD). He often speaks at community gatherings and conferences. He published The DevOps Toolkit Series and Test-Driven Java Development. His random thoughts and tutorials can be found in his blog TechnologyConversations.com.

Talk

Ten Commandments Of GitOps Applied To Continuous Delivery

We (humans) tend to follow our own rules unless some higher power defines them for us. Well… He did tell us that there are ten commandments we must follow, so we’ll explore them, we’ll memorize them, and we’ll make sure that we follow them without hesitation. Otherwise, everything will fall apart, and we will end up in the bad place.

We’ll learn about the **ten commandments of GitOps applied To continuous delivery**. We’ll see why **the processes employed in Continuous Delivery and DevOps are similar to how Buckingham Palace operates and are very different from Hogwarts School of Witchcraft and Wizardry**. We’ll also argue that **slavery is a good thing, as long as it does not involve humans**, that **being aristocracy is better than to work at a nail salon**, and that **butler is the essential role without which our system would fall apart**. Believe it or not, all that will lead us to establish practices that will significantly improve the way we work.

Session Keywords

GitOps
Kubernetes
Jenkins X
CD

Workshop

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.