GitHub materials: If you’d like to follow the code examples in this IBM Redbooks publication, you can download the GitHub repository of this book. See Appendix B, “Additional material” on page 365 for instructions.

Note: In the following images, the clusters represent minimal IBM Cloud Private configurations. Actual production configurations can vary.

Note: You can use a single boot node for multiple clusters. In such a case, the boot and master cannot be on a single node. Each cluster must have its master node. On the boot node, you must have a separate installation directory for each cluster. If you are providing your own certificate authority (CA) for authentication, you must have a separate CA domain for each cluster.

Note: if you do not specify a separate proxy, management, or etcd node, those components are also handled by the master node.

Supported platforms: For the most recent information on supported platforms for each IBM Cloud Private version 3.1.2 node type, see the Supported operating systems and platforms IBM Knowledge Center link.

IBM Cloud Private for Data: In addition to these IBM Cloud Private Editions, there is another related product called IBM Cloud Private for Data. This product is a native cloud solution that enables you to put your data to work quickly and efficiently. It lets you do both by enabling you to connect to your data (no matter where it lives), govern it, find it, and use it for analysis. IBM Cloud Private for Data also enables all of your data users to collaborate from a single, unified interface, so your IT department doesn’t need to deploy and connect multiple applications. We will not discuss this product in this document. You can see the product page at https://www.ibm.com/analytics/cloud-private-for-data for more information.

Note: Reclaim policy and Access Modes may be defined differently by each storage provider implementation.

IBM Cloud Private term	Definition
airgap environment	A network environment that does not have internet access.
API key	A unique code that is passed to an API to identify the calling application or user. An API key is used to track and control how the API is being used, for example, to prevent malicious use or abuse of the API.
application log (applog)	A log that is produced from applications that are deployed in the Cloud Foundry environment.
application	One or more computer programs or software components that provide a function in direct support of a specific business process or processes.
audit log	A log file containing a record of system events and responses.
Availability Zone	An operator-assigned, functionally independent segment of network infrastructure.
boot node	A node that is used for running installation, configuration, node scaling, and cluster updates.
buildpack	A collection of scripts that provide framework and runtime support for apps.
catalog	A centralized location that can be used to browse for and install packages in a cluster.
Cloud Foundry deployment tool	The user interface that is used to manage the deployment of Cloud Foundry.
cluster	A set of resources, worker nodes, networks, and storage devices that keep apps highly available and ready to deploy in containers.
container image	In Docker, standalone, executable software, including code and system tools, that can be used to run an application.
container	A system construct that allows users to simultaneously run separate logical operating system instances. Containers use layers of file systems to minimize image sizes and promote reuse.
deployment	A process that retrieves the output of a build, packages the output with configuration properties, and installs the package in a pre-defined location so that it can be tested or run.
Docker	An open platform that developers and system administrators can use to build, ship, and run distributed applications.
ELK stack	The three products, Elasticsearch, Logstash, and Kibana, that comprise a stack of tools that stream, store, search, and monitor data, including logs.
endpoint	A network destination address that is exposed by Kubernetes resources, such as services and ingresses.
extension	A package that contains a deployment process and its required scripts and files.
fault tolerance	The ability of a system to continue to operate effectively after the failure of a component part.
Helm chart	A Helm package that contains information for installing a set of Kubernetes resources into a Kubernetes cluster.
Helm release	An instance of a Helm chart that runs in a Kubernetes cluster.
Helm repository	A collection of charts.
high availability	The ability of IT services to withstand all outages and continue providing processing capability according to some predefined service level. Covered outages include both planned events, such as maintenance and backups, and unplanned events, such as software failures, hardware failures, power failures, and disasters.
image manager	A centralized location for managing images inside a cluster.
image	A file system and its execution parameters that are used within a container runtime to create a container. The file system consists of a series of layers, combined at runtime, that are created as the image is built by successive updates. The image does not retain state as the container executes.
inception container	See “installer container.”
ingress	A collection of rules to allow inbound connections to the Kubernetes cluster services.
installer container	The Docker container that runs the configuration manager and the Cloud Foundry deployment tool.
isolation segment	A division that can be used to separate applications as if they were in different deployments without the need for redundant management and network complexity.
isolation	The process of confining workload deployments to dedicated virtual and physical resources to achieve multi-tenancy support.
Kubernetes	An open-source orchestration tool for containers.
layer	A changed version of a parent image. Images consist of layers, where the changed version is layered on top of the parent image to create the new image.
load balancer	Software or hardware that distributes workload across a set of servers to ensure that servers are not overloaded. The load balancer also directs users to another server if the initial server fails.
machine type	A configuration that is used to instantiate a virtual machine.
management console	The graphical user interface for IBM Cloud Private.
management logging service	An ELK stack that is used to collect and store all Docker-captured logs.
management node	An optional node that only hosts management services such as monitoring, metering, and logging and can be used to prevent the master node from becoming overloaded.
marketplace	A list of enabled services from which users can provision resources.
master node	A node that provides management services and controls the worker nodes in a cluster. Master nodes host processes that are responsible for resource allocation, state maintenance, scheduling, and monitoring.
mesh	A network topology in which devices are connected with many redundant interconnections between network nodes. Every node has a connection to every other node in the network.
microclimate	An end-to-end, cloud-native solution for creating, building, testing, and deploying applications.
microservice	A set of small, independent architectural components, each with a single purpose, that communicate over a common lightweight API.
multicloud	A cloud computing model in which an enterprise uses a combination of on-premises, private cloud, and public cloud architecture.
Network File System	A protocol that allows a computer to access files over a network as if they were on its local disks.
organization (org)	In Cloud Foundry, the top-most meta object within the infrastructure that is managed by an account with administrative privileges.
persistent volume claim	A request for cluster storage.
persistent volume	Networked storage in a cluster that is provisioned by an administrator.
placement policy	A policy that defines where the application components should be deployed and how many replicas there should be.
Pod Security Policy	A policy that is used to set up cluster-level control over what a pod can do or what it can access.
pod	A group of containers that are running on a Kubernetes cluster. A pod is a runnable unit of work, which can be a either a stand-alone application or a microservice.
proxy node	A node that transmits external requests to the services that are created inside a cluster.
registry	A public or private container image storage and distribution service.
repository	A persistent storage area for data and other application resources.
resource	A physical or logical component that can be provisioned or reserved for an application or service instance. Examples of resources include database, accounts, and processor, memory, and storage limits.
role-based access control	The process of restricting integral components of a system based on user authentication, roles, and permissions.
service broker	A component of a service that implements a catalog of offerings and service plans, and interprets calls for provisioning and deprovisioning, binding and unbinding.
storage node	A node that is used to provide the backend storage and file system to store the data in a system.
system log (syslog)	A log that is produced by Cloud Foundry components.
taint	To mark a particular input, such as a variable, as being unsafe in order to subject it to security checking.
team	An entity that groups users and resources.
vCPU	A virtual core that is assigned to a virtual machine or a physical processor core if the server isn’t partitioned for virtual machines.
Virtual Machine File System (VMFS)	A cluster file system that allows virtualization to scale beyond a single node for multiple VMware ESX servers.
virtual storage area network (VSAN)	A fabric within the storage area network (SAN).
worker node	In a cluster, a physical or virtual machine that carries the deployments and services that make up an app.
workload	A collection of virtual servers that perform a customer-defined collective purpose. A workload generally can be viewed as a multitiered application. Each workload is associated with a set of policies that define performance and energy consumption goals.

---