The Service Catalog component adds the following Kubernetes resources: The service broker is a component that implements the service broker API to view the  available services and plans, create an instance from the available services and plans, and  create bindings to connect to the service instance.  Helm is a package manager. Package managers automate the process of installing,  configuring, upgrading, and removing applications on a Kubernetes cluster. An application in Kubernetes typically consists of at least two resource types: a deployment  resource, which describes a set of pods to be deployed together, and a services resource,  which defines endpoints for accessing the APIs in those pods. The application can also  include ConfigMaps, Secrets, and Ingress. For any application deployment, several Kubernetes commands ( kubectl ) are needed to  create and configure resources. Instead of manually creating each application dependency  resource separately, Helm creates many resources with one command. A Helm chart defines  several Kubernetes resources as a set in a  YAML  file. A default chart contains a minimum of  a deployment template and a service template.  Helm has two elements. A client ( Helm ) and a server ( Tiller ). The server element runs inside  a Kubernetes cluster and manages the installation of the charts. Figure 1-15 on page 20  shows how Helm components are related to each other. 1.5 Helm 1.5.1 Helm components and terminology GLYPH<SM590000> ClusterServiceBrokers GLYPH<SM590000> ClusterServiceClasses GLYPH<SM590000> ClusterServicePlans GLYPH<SM590000> ServiceInstances GLYPH<SM590000> ServiceBindings Chapter 1. Introduction to IBM Cloud Private  19