Build packs and overriding values Jenkins X offers a number of different kinds of build packs for projects including Go, Node.js, and Spring Boot. In es- sence, build packs are quickstarts for creating Kubernetes clusters. While it is typical to allow Jenkins X to automatically per- form the standard setup, there are times when you will need to override a pre-set configuration. The override function is a feature of Helm that allows de- velopers to override standard configurations. For exam- ple, you may have an application running in a staging en- vironment. If it is in this staging environment, you do not need the application to be highly available. However, when you are ready to move that application into produc- tion it must be highly available so you will want to change the availability level. This overriding will be done within GitOps (discussed in Chapter 5). There are other situa- tions when you need to be able to allocate more memory or storage space. However, these overrides are the excep- tion and should be used sparingly. Enterprise deployments As we’ve discussed, the goal of Jenkins X is to provide de- velopers with a quick way to start building cloud native applications and getting started with Kubernetes. Devel- opers have to understand how to promote applications into production using GitOps. As you recall from Chapter 5, promoting an application means to either automati- cally or manually moving the application along your pipeline to the next stage. To support the needs of enter- prise teams, Jenkins X includes a number of features, 68