Setting up your Kubernetes cluster and local workstation
Set up your Kubernetes cluster and ensure that
the required tools are installed on your local workstation.
Setting up your cluster
If you do not already have one available, create the cluster in which you want to install IBM App Connect.
For information about the system requirements, see Supported operating environment for Kubernetes.
App Connect makes use of Kubernetes secrets. These secrets are stored by etcd and are not encrypted by default. To enable encryption of etcd data for your cluster, see Encrypting Secret Data at Rest in the Kubernetes documentation.
Installing tools for managing the cluster, containers, and other resources
A set of tools can be used to manage the cluster, containers, and other resources.
Procedure
Install the following tools on your local workstation (if they are not yet installed):
- Download and install the command-line interface (CLI) tool for logging in to your Kubernetes environment; for example, Azure CLI (az) if using an Azure Kubernetes Service (AKS) cluster.
- Kubernetes CLI (kubectl): Download and install the Kubernetes CLI to run commands against your cluster. For installation instructions, see Install and Set Up kubectl in the Kubernetes documentation.
- Operator SDK: Download and install a supported version of Operator SDK, which is part of the open source Operator Framework that provides tools for building and managing Operators. For installation instructions, see Install from GitHub release in the Operator SDK documentation.
- Helm CLI (helm): Download and install the Helm CLI if you want to use helm (rather than other available methods) to install an ingress controller. (An ingress controller will be required to expose your deployed App Connect instances to external traffic as described in Creating ingress definitions for external access to your IBM App Connect instances.) For installation instructions about the Helm CLI, see Introduction to Helm in the Helm documentation.