and configuration of tools to keeping individual tools current. Jenkins X includes a single jx command line that is the entry point for getting started to create a Kuber- netes cluster. The environment is architected so that each team has its own instance of Jenkins X. With these individual instances, each team is able to see their own pipelines in the user interface. This approach means that each team has its own Kubernetes-built pods (individual or multiple containers). In this way, teams can operate at their own pace and don’t have to line up behind the entire organization’s application pipeline. Core elements of Jenkins X and supported tools As an opinionated platform, Jenkins X contains a number of elements designed to help accelerate CI/CD on Kuber- netes. These elements include: Helm. A package manager for Kubernetes that allows teams to more easily install and upgrade applications. Helm uses Helm Charts to help developers define, in- stall and upgrade Kubernetes applications. Prow. Prow is a collection of utilities used to interact with Git events and schedule build engines. Compo- nents include a scalable webhook event handler, auto- mated pull request merger and many plugins to aid a developer’s experience. Secrets. Most applications contain configuration files that handle passwords and other confidential infor- mation in the completed application. Jenkins X con 57