Installing on IBM Cloud Private

Install Event Streams on IBM Cloud Private as follows.

Before you begin

Ensure you have set up your environment according to the prerequisites, including your IBM Cloud Private environment.
Ensure you have planned for your installation, such as planning for persistent volumes if required, and creating a ConfigMap for Kafka static configuration.
Gather the following information from your administrator:
- The master host and port for your IBM Cloud Private cluster. These values are set during the installation of IBM Cloud Private. The default port is 8443. Make a note of these values, and enter them in the steps that have https://<Cluster Master Host>:<Cluster Master API Port>
- The SSH password if you are connecting remotely to the master host of your IBM Cloud Private cluster.
Ensure your proxy address uses lowercase characters. This is a setting that often needs to be checked when installing Event Streams on an IBM Cloud Private cluster deployed on Amazon Web Services (AWS). If the address is in uppercase, edit the ibmcloud-cluster-info ConfigMap in the kube-public namespace, and change the uppercase characters to lowercase for the proxy_address parameter:
kubectl edit configmap -n ibmcloud-cluster-info -n kube-public
Ensure you have the IBM Cloud Private monitoring service installed. Usually monitoring is installed by default. However, some deployment methods might not install it. For example, monitoring might not be part of the default deployment when installing IBM Cloud Private on Azure by using Terraform. Without this service, parts of the Event Streams UI do not work. You can install the monitoring service from the Catalog or CLI for existing deployments.

Preparing the platform

Prepare your platform for installing Event Streams as follows.

Create a namespace

You must use a namespace that is dedicated to your Event Streams deployment. This is required because Event Streams uses network security policies to restrict network connections between its internal components.

If you plan to have multiple Event Streams instances, create namespaces to organize your Event Streams deployments into, and control user access to them.

To create a namespace, you must have the Cluster Administrator role.

Log in to your IBM Cloud Private cluster management console as an administrator. For more information, see the IBM Cloud Private documentation.
Ensure you log in as a user that has the Cluster Administrator role.
From the navigation menu, click Manage > Namespaces.
Click Create Namespace.
Enter a name for your namespace.
Ensure you have the ibm-restricted-psp PodSecurityPolicy selected for the target namespace.
Click Create.

See the IBM Cloud Private documentation for more information about creating namespaces.

Download the archive

Download the Event Streams installation image file from the IBM Passport Advantage site and make it available in your catalog.

Go to IBM Passport Advantage, and search for “Event Streams”. Download the images related to the part numbers for your platform.
Ensure you configure your Docker CLI to access your cluster.
Log in to your cluster from the IBM Cloud Private CLI and log in to the Docker private image registry:
```
cloudctl login -a https://<cluster_CA_domain>:8443
docker login <cluster_CA_domain>:8500
```
Note: The default value for the cluster_CA_domain parameter is mycluster.icp. If necessary add an entry to your system’s host file to allow it to be resolved. For more information, see the IBM Cloud Private documentation.
Make the Event Streams Helm chart available in the catalog by using the compressed image you downloaded from IBM Passport Advantage.
cloudctl catalog load-archive --archive <PPA-image-name.tar.gz>

When the image installation completes successfully, the catalog is updated with the Event Streams local chart, and the internal Docker repository is populated with the Docker images used by Event Streams.

Preparing the repository

Prepare your repository by creating an image policy.

Note: You only need to follow these steps if the image-security-enforcement service is enabled. If the service is not enabled, you can ignore these steps.

The following steps require you to run kubectl commands. To run the commands, you must be logged in to your IBM Cloud Private cluster as an administrator.

Log in to your cluster as an administrator by using the IBM Cloud Private CLI:
cloudctl login -a https://<cluster-address>:<cluster-router-https-port> The default port is 8443.

Create an image policy for the internal Docker repository. The policy enables images to be retrieved during installation.

To create an image policy:

Create a .yaml file with the following content, then replace <cluster_CA_domain> with the correct value for your IBM Cloud Private environment, and replace the <namespace_for_event_streams> value with the name where you intend to install Event Streams (set as -n event-streams in the previous example):
```
apiVersion: securityenforcement.admission.cloud.ibm.com/v1beta1
kind: ImagePolicy
metadata:
  name: image-policy
  namespace: <namespace_for_event_streams>
spec:
  repositories:
  - name: docker.io/*
    policy: null
  - name: <cluster_CA_domain>:8500/*
    policy: null
```
Run the following command: kubectl apply -f <filename>.yaml

For more information about container image security, see the IBM Cloud Private documentation.

Installing the Event Streams chart

Install the Event Streams chart as follows.

Log in to your IBM Cloud Private cluster management console as an administrator. For more information, see the IBM Cloud Private documentation.
Ensure you log in as a user that has the Team Administrator or Cluster Administrator role.
Click Catalog in the top navigation menu.
Search for ibm-eventstreams-prod and select it from the result. The Event Streams README is displayed.
Click Configure.
Note: The README includes information about how to install Event Streams by using the CLI. To use the CLI, follow the instructions in the README instead of clicking Configure.
Enter a release name that identifies your Event Streams installation, select the target namespace you created previously, select a target cluster (for example, local-cluster), and accept the terms of the license agreement.
Expand the All parameters section to configure the settings for your installation as described in configuring. Configuration options to consider include setting up persistent storage, external access, and preparing for geo-replication.
Click Install.
Verify your installation and consider other post-installation tasks.