Jenkins X Workshop

Created by Joost van der Griendt

Based on the work of Jenkins X and Viktor Farcic

## whomai

### Joost van der Griendt * Work for CloudBees * Professional Services Consultant EMEA * Hail from Utrecht, The Netherlands * Call me `Jay`

### background * Java developer * CI/CD * Jenkins / Nexus / Sonar * Docker / Docker Swarm / Kubernetes

### Kenny Younger * Work for CloudBees * Technical Success Manager U.S.A. * Recently moved to Fort Worth, TX

### background * Software Engineer * Spring Boot / Apache Camel / BDD * OSS Jenkins (on Windows!)

This presentation

Workshop material

TL;DR

## It's become difficult * Maybe not rocket science<!-- .element: class="fragment" --> * But no longer trivial<!-- .element: class="fragment" --> * Yet, it should be simple...<!-- .element: class="fragment" -->

> You do not need to understand Kubernetes to use Jenkins X. Jenkins X allows us to harness the power of Kubernetes without spending an eternity learning the ever-growing list of the things it does.

My Journey to JX

## The Beginning * Jenkins * Nexus * Sonar

## Evolution * VM's & Bash<!-- .element: class="fragment" --> * VM's & Ansible<!-- .element: class="fragment" --> * CoW<!-- .element: class="fragment" --> * Fabric8<!-- .element: class="fragment" --> * Manatee & CIDC<!-- .element: class="fragment" --> * Jenkins X<!-- .element: class="fragment" -->

SDLC

## SDLC **S**oftware **D**evelopment **L**ife**C**ycle * People<!-- .element: class="fragment" --> * Process<!-- .element: class="fragment" --> * Technology<!-- .element: class="fragment" --> > From inception till it is OUT of Production.

## SDLC * Self-Service Dev Platform<!-- .element: class="fragment" --> * CI/CD, Agile, DevOps, DevSecOps<!-- .element: class="fragment" --> * Observability<!-- .element: class="fragment" --> * (Best) Practices<!-- .element: class="fragment" --> * Developer Productivity<!-- .element: class="fragment" -->

CICD

## CI/CD * Continous Integration<!-- .element: class="fragment" --> * Continous Delivery<!-- .element: class="fragment" --> * Continous Deployment<!-- .element: class="fragment" --> * Continous everything<!-- .element: class="fragment" --> * Progressive Delivery<!-- .element: class="fragment" --> * GitOps...<!-- .element: class="fragment" -->

### 10 Commandments * be agile<!-- .element: class="fragment" --> * refactor<!-- .element: class="fragment" --> * educate everyone<!-- .element: class="fragment" --> * small teams / codebase<!-- .element: class="fragment" --> * TDD<!-- .element: class="fragment" -->

### 10 Commandments * everything-as-code<!-- .element: class="fragment" --> * fast<!-- .element: class="fragment" --> * pipeline = production<!-- .element: class="fragment" --> * run build before commit<!-- .element: class="fragment" --> * trunk based development<!-- .element: class="fragment" -->

## Today's requirements * It needs to be cloud-native<!-- .element: class="fragment" --> * It needs to be cloud-agnostic<!-- .element: class="fragment" --> * It needs to scale from zero to how much I need<!-- .element: class="fragment" --> * It needs to follow the everything-as-code principle<!-- .element: class="fragment" --> * Everything needs to integrate with everything<!-- .element: class="fragment" --> * It needs to be fast<!-- .element: class="fragment" --> * It needs to "just work"<!-- .element: class="fragment" -->

### How * adopt containerization<!-- .element: class="fragment" --> * adopt schedulers<!-- .element: class="fragment" --> * adopt serverless<!-- .element: class="fragment" --> * re-evaluate tools<!-- .element: class="fragment" --> * use tools for your workflow<!-- .element: class="fragment" --> * batteries included but swappable<!-- .element: class="fragment" -->

### How exactly? * Kubernetes<!-- .element: class="fragment" --> * Jenkins X (Serverless)<!-- .element: class="fragment" --> * GitOps (JX Or Prow)<!-- .element: class="fragment" --> * Helm (or drop-in replacement)<!-- .element: class="fragment" --> * Extend to suit your needs<!-- .element: class="fragment" -->

## Pipelines

Kubernetes - Intro

## Kubernetes, what? > Kubernetes is a portable, extensible open-source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation. It has a large, rapidly growing ecosystem. Kubernetes services, support, and tools are widely available.

## Kubernetes, why? * Built on ops experience<!-- .element: class="fragment" --> * Modular<!-- .element: class="fragment" --> * API first<!-- .element: class="fragment" --> * Standardization<!-- .element: class="fragment" --> * Container Orchestration<!-- .element: class="fragment" --> * Proven<!-- .element: class="fragment" -->

## Even if you don't need scaling * explicit resource reqs<!-- .element: class="fragment" --> * auto-restarts<!-- .element: class="fragment" --> * homogenous deployment<!-- .element: class="fragment" --> * homogenous observability<!-- .element: class="fragment" --> * homogenous extension<!-- .element: class="fragment" -->

## Kubernetes, How? * Declarative instead of Imperative<!-- .element: class="fragment" --> * Self-healing<!-- .element: class="fragment" --> * High-Availability (HA)<!-- .element: class="fragment" --> * Dynamic sizing & scaling<!-- .element: class="fragment" --> * Immutable<!-- .element: class="fragment" --> * Separate state from process<!-- .element: class="fragment" --> * 12-factor app/container

## Kubernetes, How? * Standard but Extensible<!-- .element: class="fragment" --> * Better utilization<!-- .element: class="fragment" --> * Serverless even better * but more expensive for _predictable load_ * Dynamic Service Discovery<!-- .element: class="fragment" --> * Batteries included but swappable<!-- .element: class="fragment" --> * Layers of Abstraction<!-- .element: class="fragment" -->

### Cluster thinking * Pets vs Cattle<!-- .element: class="fragment" --> * Declarative<!-- .element: class="fragment" --> * Infrastructure As Code++<!-- .element: class="fragment" --> * Immutable<!-- .element: class="fragment" --> * Separate state from process<!-- .element: class="fragment" --> * Observability = function of cluster <!-- .element: class="fragment" -->

## Kubernetes Basics * Workloads<!-- .element: class="fragment" --> * Services<!-- .element: class="fragment" --> * Networking<!-- .element: class="fragment" --> * ResourceManagement<!-- .element: class="fragment" --> * Storage<!-- .element: class="fragment" --> * LifeCycle<!-- .element: class="fragment" --> * Scheduling<!-- .element: class="fragment" -->

## Workloads * Pod<!-- .element: class="fragment" --> * DaemonSet<!-- .element: class="fragment" --> * ReplicaSet<!-- .element: class="fragment" --> * Deployment<!-- .element: class="fragment" --> * StatefulSet<!-- .element: class="fragment" --> * (Cron)Jobs<!-- .element: class="fragment" -->

Kubernetes Part I

## Pod > A Pod is the basic building block of Kubernetes–the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster.

### Pod * Basic building block<!-- .element: class="fragment" --> * Use (only) with other abstractions<!-- .element: class="fragment" --> * Fungable<!-- .element: class="fragment" --> * 1 Pod = 1 IP<!-- .element: class="fragment" -->

## DaemonSet > A DaemonSet ensures that all (or some) Nodes run a copy of a Pod. As nodes are added to the cluster, Pods are added to them.

### DaemonSet - When * cluster storage, such as glusterd, ceph, on each node<!-- .element: class="fragment" --> * logs collection, such as fluentd or logstash<!-- .element: class="fragment" --> * monitoring...<!-- .element: class="fragment" -->

## ReplicaSet > A ReplicaSet’s purpose is to maintain a stable set of replica Pods running at any given time

### ReplicaSet * Guarantees x-amount of pods running<!-- .element: class="fragment" --> * Generally not used directly<!-- .element: class="fragment" --> * Building block of Deployment<!-- .element: class="fragment" -->

## Job > A Job creates one or more Pods and ensures that a specified number of them successfully terminate.

## CronJob > One CronJob object is like one line of a crontab (cron table) file. It runs a job periodically on a given schedule, written in Cron format

## Labels > Labels are key/value pairs that are attached to objects, such as pods.

## Labels > Labels can be used to organize and to select subsets of objects.

## Labels * Example: pod has label 'app=myapp'<!-- .element: class="fragment" --> * `kubectl get pods -l app=myapp`<!-- .element: class="fragment" --> * Services & Deployments map to Labels<!-- .element: class="fragment" --> * In this case, we call it a: selector<!-- .element: class="fragment" -->

## Labels ```YAML spec: selector: matchLabels: app: jenkins ```

## Service > A Kubernetes Service is an abstraction which defines a logical set of Pods and a policy by which to access them - sometimes called a micro-service. The set of Pods targeted by a Service is determined by a Label Selector.

### Service * Routes communication between pods<!-- .element: class="fragment" --> * Routes communication between external and pod<!-- .element: class="fragment" --> * Has its own DNS name<!-- .element: class="fragment" --> * Registers its connected pods to an endpoint<!-- .element: class="fragment" -->

## Deployment > You describe a desired state in a Deployment object, and the Deployment controller changes the actual state to the desired state at a controlled rate.

### Deployment * The workhorse of Kubernetes<!-- .element: class="fragment" --> * Manages ReplicaSet (& Pod)<!-- .element: class="fragment" --> * Generally combined with a Service<!-- .element: class="fragment" --> * Abstraction of choice to build on-top<!-- .element: class="fragment" -->

## Ingress > An API object that manages external access to the services in a cluster, typically HTTP. > Ingress can provide load balancing, SSL termination and name-based virtual hosting.

### Ingress * LoadBalancer for routing<!-- .element: class="fragment" --> * Can create LB's via CloudController<!-- .element: class="fragment" --> * Several ways of using<!-- .element: class="fragment" --> * Several implementations<!-- .element: class="fragment" -->

### Ingress - Ways of using * NodePort / LoadBalancer (Public Cloud Provider)<!-- .element: class="fragment" --> * Path based<!-- .element: class="fragment" --> * Host (Domain) based<!-- .element: class="fragment" --> * Default<!-- .element: class="fragment" -->

### Ingress - Implementations * Nginx Ingress<!-- .element: class="fragment" --> * Traefik<!-- .element: class="fragment" --> * Gloo<!-- .element: class="fragment" --> * others...<!-- .element: class="fragment" -->

Kubernetes Part II

## Kubernetes Architecture

## Controllers > Controller can create and manage multiple Pods for you, handling replication and rollout and providing self-healing capabilities at cluster scope.

## ConfigMaps > ConfigMaps bind configuration files, command-line arguments, environment variables, port numbers, and other configuration artifacts to your Pods' containers and system components at runtime.

### ConfigMaps * Separate config from Pods<!-- .element: class="fragment" --> * Update config separately<!-- .element: class="fragment" --> * Allows overriding container defaults<!-- .element: class="fragment" --> * Do **not** use for confidential data!<!-- .element: class="fragment" -->

### ConfigMaps * from files<!-- .element: class="fragment" --> * from literals<!-- .element: class="fragment" --> * from environment files<!-- .element: class="fragment" -->

## Secrets > A Secret is an object that contains a small amount of sensitive data such as a password, a token, or a key.

### Secrets * from literal<!-- .element: class="fragment" --> * usename & password<!-- .element: class="fragment" --> * from file<!-- .element: class="fragment" --> * docker pull credentials<!-- .element: class="fragment" --> * certificates<!-- .element: class="fragment" -->

## Namespaces > Kubernetes supports multiple virtual clusters backed by the same physical cluster. These virtual clusters are called namespaces.

### Namespaces * there is always a 'default'<!-- .element: class="fragment" --> * there are a few namespaces by default<!-- .element: class="fragment" --> * helps separate users or environments<!-- .element: class="fragment" --> * is part of K8S DNS structuring<!-- .element: class="fragment" -->

### Namespaces * is part of your **context**<!-- .element: class="fragment" --> * there are tools who help with this<!-- .element: class="fragment" --> * including jx<!-- .element: class="fragment" -->

## Securing Kubernetes * Users<!-- .element: class="fragment" --> * ServiceAccounts<!-- .element: class="fragment" --> * Roles<!-- .element: class="fragment" --> * ClusterRoles<!-- .element: class="fragment" --> * RoleBinding<!-- .element: class="fragment" --> * ClusterRoleBinding<!-- .element: class="fragment" -->

## ResourceManagement * Memory<!-- .element: class="fragment" --> * CPU <!-- .element: class="fragment" --> * Requests & Limits<!-- .element: class="fragment" --> * QoS: best effort, guaranteed, burst<!-- .element: class="fragment" -->

Kubernetes Part III

## Storage * Volumes<!-- .element: class="fragment" --> * Persistent Volumes<!-- .element: class="fragment" --> * Persistent Volume Claim<!-- .element: class="fragment" --> * Persistent Volume Claim Template<!-- .element: class="fragment" -->

### Volume * StorageClasses<!-- .element: class="fragment" --> * Provisioners<!-- .element: class="fragment" --> * Types of volumes<!-- .element: class="fragment" -->

### Volume Types<!-- .element: class="fragment" --> * emptyDir<!-- .element: class="fragment" --> * configMap<!-- .element: class="fragment" --> * local<!-- .element: class="fragment" --> * nfs<!-- .element: class="fragment" --> * [many more](https://kubernetes.io/docs/concepts/storage/volumes/#types-of-volumes)<!-- .element: class="fragment" -->

## StatefulSet > Like a Deployment , a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of their Pods.

### StatefulSet * used for stateful applications<!-- .element: class="fragment" --> * wraps around ReplicaSet<!-- .element: class="fragment" --> * uses volumes differently<!-- .element: class="fragment" --> * manages pods differently<!-- .element: class="fragment" -->

GitOps

## GitOps > *GitOps* is a way to do Continuous Delivery. It works by using Git as a single source of truth for declarative infrastructure and applications. With Git at the center of your delivery pipelines, developers can make pull requests to accelerate and simplify application deployments and operations tasks to Kubernetes. - WeaveNet

### Principles * entire system described declaratively<!-- .element: class="fragment" --> * canonical desired system state versioned in Git<!-- .element: class="fragment" --> * approved changes can be applied automatically<!-- .element: class="fragment" --> * agents to ensure correctness now and over time<!-- .element: class="fragment" -->

### What it comes down to * Git == Single Source of Truth<!-- .element: class="fragment" --> * Changes are managed via Git<!-- .element: class="fragment" --> * Effectuated by a pipeline listening to Git<!-- .element: class="fragment" --> * Asynchronous, Decoupled and Explicit<!-- .element: class="fragment" --> * Audit log & rights<!-- .element: class="fragment" -->

Jenkins X - Intro

> You do not need to understand Kubernetes to use Jenkins X. Jenkins X allows us to harness the power of Kubernetes without spending eternity learning the ever-growing list of the things it does.

## Jenkins X - Introduction * What is Jenkins Jenkins X<!-- .element: class="fragment" --> * Environments<!-- .element: class="fragment" --> * Pipelines<!-- .element: class="fragment" --> * Differences with Jenkins<!-- .element: class="fragment" --> * Core components<!-- .element: class="fragment" -->

### What is Jenkins X * Opinionated<!-- .element: class="fragment" --> * Re-imagining how to do CI/CD<!-- .element: class="fragment" --> * CLI<!-- .element: class="fragment" --> * Kubernetes first<!-- .element: class="fragment" --> * Based on standards<!-- .element: class="fragment" -->

### Opinions * Use Git & Kubernetes<!-- .element: class="fragment" --> * Trunk Based Development + PR's<!-- .element: class="fragment" --> * You don't need a UI<!-- .element: class="fragment" --> * Use Kubernetes, not understand it<!-- .element: class="fragment" --> * Leverage existing tools<!-- .element: class="fragment" -->

### CLI * Wrapper for Cloud CLI's<!-- .element: class="fragment" --> * Wrapper for Kubernetes tools<!-- .element: class="fragment" --> * Manage Jenkins X installation<!-- .element: class="fragment" --> * Pipeline automation<!-- .element: class="fragment" -->

### Kubernetes Native * Use Kubernetes primitives<!-- .element: class="fragment" --> * Extended with CRD's<!-- .element: class="fragment" --> * Git & Kubernetes is all you need<!-- .element: class="fragment" --> * Following evolving practices/eco system<!-- .element: class="fragment" -->

### Based on Standards * Use (defacto) standards<!-- .element: class="fragment" --> * Use eco system's most used tools <!-- .element: class="fragment" --> * Working with CDF to create new standards<!-- .element: class="fragment" -->

### Environments * dev = your machine + jx namespace<!-- .element: class="fragment" --> * staging<!-- .element: class="fragment" --> * production<!-- .element: class="fragment" --> * preview<!-- .element: class="fragment" --> * on-demand-just-for-test<!-- .element: class="fragment" -->

### Pipelines * as code -> Jenkinsfile<!-- .element: class="fragment" --> * containerized<!-- .element: class="fragment" --> * pipeline/multi-branch/github org<!-- .element: class="fragment" --> * best practices<!-- .element: class="fragment" -->

### Pipeline - Best Practices * use shell<!-- .element: class="fragment" --> * able to run locally<!-- .element: class="fragment" --> * declarative format<!-- .element: class="fragment" --> * jx step<!-- .element: class="fragment" -->

### Differences with Jenkins * Only runs on Kubernetes<!-- .element: class="fragment" --> * Opinionated<!-- .element: class="fragment" --> * Does not rely on plugins<!-- .element: class="fragment" --> * CLI / API first<!-- .element: class="fragment" --> * More than CI<!-- .element: class="fragment" --> * End-to-End system<!-- .element: class="fragment" --> * Can be serverless<!-- .element: class="fragment" --> * Works out-of-the-box<!-- .element: class="fragment" -->

### Core components * jx CLI<!-- .element: class="fragment" --> * Helm<!-- .element: class="fragment" --> * Kubernetes<!-- .element: class="fragment" --> * CRD's & Namespaces<!-- .element: class="fragment" --> * Docker Registry<!-- .element: class="fragment" --> * Chartmuseum & Monocular<!-- .element: class="fragment" --> * Nexus<!-- .element: class="fragment" --> * Skaffold<!-- .element: class="fragment" --> * Draft & BuildPacks<!-- .element: class="fragment" --> * Jenkins<!-- .element: class="fragment" -->

### Practices * Loosely-coupled Architectures<!-- .element: class="fragment" --> * Self-service Configuration<!-- .element: class="fragment" --> * Automated Provisioning<!-- .element: class="fragment" --> * Continuous Build / Integration and Delivery<!-- .element: class="fragment" --> * Automated Release Management<!-- .element: class="fragment" --> * Incremental Testing<!-- .element: class="fragment" --> * Infrastructure Configuration as Code<!-- .element: class="fragment" --> * Comprehensive configuration management<!-- .element: class="fragment" --> * Trunk based development and feature flags<!-- .element: class="fragment" -->

Jenkins X - Install

## Jenkins X - Install * from scratch<!-- .element: class="fragment" --> * via Terraform or cloud CLI<!-- .element: class="fragment" --> * in existing cluster<!-- .element: class="fragment" --> * GitOps for JX (experimental)<!-- .element: class="fragment" -->

### Install Process * install missing CLI's * install cloud provider CLI * create Kubernets cluster * create `jx` namespace * install Tiller (optional) * setup ingress controller * configure Git repositories * configure secrets * install tools via Helm

### Install Configuration * disable Nexus * disable Chartmuseum * alternative Jenkins image * alternative Docker Registry * alternative Git provider

## Jenkins X - Go demo * create JX managed application<!-- .element: class="fragment" --> * deploy to staging<!-- .element: class="fragment" --> * update via PR<!-- .element: class="fragment" --> * preview the PR<!-- .element: class="fragment" --> * merge the PR and update staging<!-- .element: class="fragment" --> * promote to production<!-- .element: class="fragment" --> * Static Jenkins!<!-- .element: class="fragment" -->

## Jenkins X - Import * add to git repo<!-- .element: class="fragment" --> * create remote git repo<!-- .element: class="fragment" --> * add any missing files from Build Pack<!-- .element: class="fragment" --> * register webhook in remote repo<!-- .element: class="fragment" --> * add git repo to your Jenkins<!-- .element: class="fragment" --> * trigger the first pipeline<!-- .element: class="fragment" -->

## Import gotchas * can ignore draft via `--no-draft`<!-- .element: class="fragment" --> * can import GitHub org via `jx import --github...`<!-- .element: class="fragment" --> * sets default branch patterns<!-- .element: class="fragment" --> * override via `--branches "abc|xyz.*|.." * and configure via `jx edit branchpattern`

### Import demo * fork an existing application<!-- .element: class="fragment" --> * import it into Jenkins X<!-- .element: class="fragment" --> * make it work<!-- .element: class="fragment" -->

## Jenkins X - Build Pack * there are standard packs<!-- .element: class="fragment" --> * JX team packs * community packs * creating your own requires some knowledge beyond `using jx`<!-- .element: class="fragment" --> * helm * draft * `jx` manages Build Packs for you<!-- .element: class="fragment" --> * in `.~/.jx/draft/packs/`

### What's inside a Build Pack * Dockerfile<!-- .element: class="fragment" --> * Jenkinsfile<!-- .element: class="fragment" --> * Helm Chart (in `charts/${APP_NAME}` folder)<!-- .element: class="fragment" --> * Preview Helm Chart (in `charts/preview`)<!-- .element: class="fragment" -->

### When to create a Build Pack * only include hard requirements<!-- .element: class="fragment" --> * leave optional things out<!-- .element: class="fragment" --> * focus on the repeatable case<!-- .element: class="fragment" --> * 1, 2, many<!-- .element: class="fragment" -->

### Create a BuildPack * what will every micronaut require?<!-- .element: class="fragment" --> * redis? maybe not<!-- .element: class="fragment" --> * different dockerfile? yes<!-- .element: class="fragment" --> * different health check endpoint? yes<!-- .element: class="fragment" -->

### Create Build Pack demo * take lessons learned from Import Demo<!-- .element: class="fragment" --> * look at standard packs<!-- .element: class="fragment" --> * copy existing<!-- .element: class="fragment" --> * adjust to fit our need<!-- .element: class="fragment" --> * re-import our forked app<!-- .element: class="fragment" --> * see if it works<!-- .element: class="fragment" -->

## Explore .jx folder * cloud-environments * environments * jenkins-x-versions * jx.lock * adminSecrets.yaml * chartmuseumAuth.yaml * gitAuth.yaml * jenkinsAuth.yaml * draft * plugins

SDLC Continued

## SDLC Continued * Versioning<!-- .element: class="fragment" --> * Package & Publish<!-- .element: class="fragment" --> * Workflows<!-- .element: class="fragment" -->

### Versioning * SemVer<!-- .element: class="fragment" --> * Automation<!-- .element: class="fragment" --> * jx-release-version<!-- .element: class="fragment" --> * Explicit Dependencies<!-- .element: class="fragment" -->

### SemVer - Old * Major<!-- .element: class="fragment" --> * Minor<!-- .element: class="fragment" --> * Patch<!-- .element: class="fragment" -->

### SemVer - CICD * Major<!-- .element: class="fragment" --> * Minor<!-- .element: class="fragment" --> * Build<!-- .element: class="fragment" -->

### Package & Publish * No rebuilding<!-- .element: class="fragment" --> * Signify release candidate<!-- .element: class="fragment" --> * Explicit Dependency Management<!-- .element: class="fragment" --> * Inspection before deployment<!-- .element: class="fragment" --> * Inspection later...t<!-- .element: class="fragment" -->

### Workflow * commit<!-- .element: class="fragment" --> * build<!-- .element: class="fragment" --> * PR<!-- .element: class="fragment" --> * preview<!-- .element: class="fragment" --> * review<!-- .element: class="fragment" --> * merge<!-- .element: class="fragment" --> * build<!-- .element: class="fragment" --> * promote<!-- .element: class="fragment" -->

The X-Files

## Mulder * fork & clone * import into jx * fix redis config * fix health check endpoint * add unit tests to pipeline * add integration tests to pipeline * test PR * test staging & production

## Scully * fork & clone * jx import * fix Dockerfile * add Mulder as dependency * helm repo stuff * fix url to Mulder * click on Scully's "voice box" to get a quote...

## Jenkins X - Dev Workflow * ??

## Jenkins X - Build With Kaniko * why?

K8S Ecosystem

## Kubernetes Ecosystem * Docker * Helm * Knative * Skaffold * Chartmuseum * Tekton

## Docker

## Helm * package manager for Kubernetes * quivalent to `yum install <package>` * Kubernetes manifest template (Go templates) * packaged and versioned, reffered to as `Charts`

### Helm - Use Cases * manages packages, repo and installs * manage dependencies to other Charts * allows for customizing installations * used as building blocks in other tools * separate packaging (Chart) from runtime (application image) * there's the chart version * and the application version

## Knative

## Skaffold

## Chartmuseum * lightweight Helm chart repository * alternatives are Artifactory, Nexus 3 * supports different storage options * local (e.g., Kubernetes volume) * S3 / Minio * Google Cloud Storage * Azure Blob Store * Alibaba Cloud OSS storage * Openstack Object Storage

## Monocular * UI for Helm repositories * includes documentation and searching * insight into charts installed via helm

## Tekton

K8S Advanced

## Kubernetes Advanced * Scheduling * Policies * Admission Controllers * Customization (CRD's) * RBAC * Platformization

## ...

Serverless Jenkins

## Jenkins X - Serverless

## Jenkins X - Extensions

## Further steps

## Resources & Credits * [Viktor Farcic](https://vfarcic.github.io/#/cover) * [exoscale.com - CI](https://www.exoscale.com/static/syslog/2018-11-08-what-is-ci/what-is-continuous-integration.png) * [WeaveNet - What is GitOps](https://www.weave.works/technologies/gitops/#what-is-gitops)