IBM Event Automation

https://ibm.github.io/event-automation
Admin
IBM Event Automation is a comprehensive platform for managing Kafka topics through Event Endpoint...
Tokens:286,482
Snippets:3,410
Trust Score:9.7
Update:5 months ago
Show doc for...
Tokens:
Raw
### Example: Install Operator to Manage All Instances

Source: https://ibm.github.io/event-automation/eem/installing/installing-on-kubernetes

This example demonstrates installing the operator to manage all Event Manager instances across any namespace, with webhook creation disabled.

```bash
helm install \
   eventendpointmanagement ibm-helm/ibm-eem-operator\
   -n "my-namespace" \
   --set watchAnyNamespace=true \
   --set webhook.create=false
```

--------------------------------

### Example: Install Operator to Watch All Namespaces

Source: https://ibm.github.io/event-automation/ep/installing/installing-on-kubernetes

This example demonstrates installing the operator to manage Event Processing instances across all namespaces, with webhook creation disabled.

```bash
helm install \
   eventprocessing ibm-helm/ibm-ep-operator\
   -n "my-namespace" \
   --set watchAnyNamespace=true \
   --set webhook.create=false
```

--------------------------------

### Example: Install Operator for a Single Namespace

Source: https://ibm.github.io/event-automation/ep/installing/installing-on-kubernetes

Install the operator for a single namespace without custom configurations for webhook or namespace watching.

```bash
helm install eventprocesssing ibm-helm/ibm-ep-operator -n "my-eventprocesssing"
```

--------------------------------

### Example Subscription Details

Source: https://ibm.github.io/event-automation/ep/installing/upgrading

This is an example output from the 'oc get subscription' command, illustrating how to identify the subscribed channel.

```text
NAME                        PACKAGE                     SOURCE                      CHANNEL
ibm-eventautomation-flink   ibm-eventautomation-flink   ea-flink-operator-catalog   v1.4
ibm-eventprocessing         ibm-eventprocessing         ea-sp-operator-catalog      v1.4
```

--------------------------------

### Example: Install CRDs in 'ep' namespace

Source: https://ibm.github.io/event-automation/ep/installing/installing-on-kubernetes

Example commands to install both Event Processing and Flink CRDs in the 'ep' namespace.

```bash
helm install ep-crds ibm-helm/ibm-ep-operator-crd -n ep
helm install ibm-flink-crds ibm-helm/ibm-eventautomation-flink-operator-crd -n ep
```

--------------------------------

### Example Operator Status Output

Source: https://ibm.github.io/event-automation/eem/installing/installing-on-kubernetes

A successful installation will show '1/1' in the READY column, indicating the operator is running correctly.

```text
NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
ibm-eem-operator                1/1     1            1           7d4h
```

--------------------------------

### Get License Service Instance Route Example

Source: https://ibm.github.io/event-automation/eem/installing/installing

An example command to retrieve the route for the `ibm-licensing-service-instance` in the `ibm-common-services` namespace.

```bash
oc get routes ibm-licensing-service-instance -n ibm-common-services -ojsonpath='{.status.ingress[*].host}'
```

--------------------------------

### Example OpenShift Subscription Output

Source: https://ibm.github.io/event-automation/eem/installing/upgrading

This is an example output from the `oc get subscription` command, showing the package, source, and crucially, the CHANNEL your subscription is configured for.

```bash
NAME                                      PACKAGE                          SOURCE                                     CHANNEL
ibm-eventendpointmanagement               ibm-eventendpointmanagement      ibm-eventendpointmanagement-catalog        v11.6
```

--------------------------------

### Example: Install Operator CRDs in a Specific Namespace

Source: https://ibm.github.io/event-automation/eem/installing/installing-on-kubernetes

Example command to install the operator CRD Helm chart in the `eem-crds` namespace.

```bash
helm install eem-crds ibm-helm/ibm-eem-operator-crd -n eem-crds
```

--------------------------------

### Example: Install Operator for a Specific Namespace

Source: https://ibm.github.io/event-automation/eem/installing/installing-on-kubernetes

Install the operator to manage Event Manager instances only within a specific namespace, using default settings for other options.

```bash
helm install eventendpointmanagement ibm-helm/ibm-eem-operator -n "my-eventendpointmanagement"
```

--------------------------------

### Install Operator to Watch Any Namespace

Source: https://ibm.github.io/event-automation/ep/installing/installing-on-kubernetes

Example command to install the operator that will manage `FlinkDeployments` in any namespace.

```bash
helm install \
   flink ibm-helm/ibm-eventautomation-flink-operator\
   -n "my-namespace" \
   --set watchAnyNamespace=true
```

--------------------------------

### Example Pod Status During Uninstallation

Source: https://ibm.github.io/event-automation/ep/installing/uninstalling

This example shows typical pod statuses ('Terminating') while an instance is being uninstalled.

```bash
$ kubectl get pods --selector app.kubernetes.io/instance=quick-start
> 
NAME                                              READY     STATUS        RESTARTS   AGE
quick-start-flink-kubernetes-65f555b884-fvtks     0/2       Terminating   0          7d17h
quick-start-flink-stream-authoring-ep-sts-0       0/1       Terminating   0          46h
quick-start-flink-ep-operator-578556d4cc-p5w58    0/1       Terminating   0          7d11h
```

--------------------------------

### Example Response for Read All User Assets

Source: https://ibm.github.io/event-automation/eem-api-117

Example structure of the response when listing all user assets.

```json
[
  {
    "userId": "string",
    "preferredUsername": "string",
    "displayName": "string",
    "roles": [
      "string"
    ],
    "assets": {
      "eventsource": 0,
      "cluster": 0,
      "option": 0,
      "subscription": 0,
      "ca": 0,
      "gateway": 0
    }
  }
]
```

--------------------------------

### Example OpenShift Route Output

Source: https://ibm.github.io/event-automation/ep/getting-started/logging-in

This is an example output from the 'oc get routes' command. The HOST/PORT value is used to construct the UI login URL.

```text
NAME                      HOST/PORT                                                         PATH    SERVICES                 PORT   TERMINATION  WILDCARD
my-event-processing-ep    my-event-processing-ep-myproject.apps.my-cluster.my-domain.com            my-event-processing-ep   3000   reencrypt     None
```

--------------------------------

### Example: Apply Production EventProcessing CR

Source: https://ibm.github.io/event-automation/ep/installing/installing

Example command to apply a production-ready EventProcessing custom resource configuration file named 'production.yaml'.

```bash
oc apply -f production.yaml
```

--------------------------------

### Example Output for Successful Event Processing Deployment

Source: https://ibm.github.io/event-automation/ep/installing/post-installation

This is an example of the expected output when an Event Processing instance is successfully deployed and running.

```bash
kubectl get eventprocessing development -n myepnamespace -o jsonpath='{.status.phase}'
Running
```

--------------------------------

### Example Apply FlinkDeployment Custom Resource

Source: https://ibm.github.io/event-automation/ep/installing/installing-on-kubernetes

Example command for applying a FlinkDeployment custom resource file named 'flinkdeployment_demo.yaml' to the 'my-flink' namespace.

```bash
kubectl apply -f flinkdeployment_demo.yaml -n my-flink
```

--------------------------------

### Example kubectl Patch Command

Source: https://ibm.github.io/event-automation/ep/security/user-roles

An example of patching the user roles secret with a specific Base64 encoded value for the 'quick-start-ep' instance.

```bash
kubectl patch secret quick-start-ep-ibm-ep-user-roles --type='json' -p='[{"op" : "replace" ,"path" : "/data/user-mapping.json" ,"value" : "ewogICJtYXBwaW5ncyI6IFsKICAgIHsKICAgICAgImlkIjogImF1dGhvcjEiLAogICAgICAicm9sZXMiOiBbCiAgICAgICAgImF1dGhvciIKICAgICAgXQogICAgfSwKICAgIHsKICAgICAgImlkIjogInZpZXdlcjEiLAogICAgICAicm9sZXMiOiBbCiAgICAgICAgInZpZXdlciIKICAgICAgXQogICAgfQogIF0KfQo="}]'
```

--------------------------------

### Install OpenSSL and gettext with Homebrew

Source: https://ibm.github.io/event-automation/eem/installing/install-docker-egw

Install required packages on macOS for certificate generation. Ensure you have Homebrew installed.

```bash
brew install gettext openssl@3

```

--------------------------------

### Install Ansible Collections

Source: https://ibm.github.io/event-automation/tutorials/guided/tutorial-0

Installs the necessary Kubernetes and general community Ansible collections required for the tutorial playbook.

```ansible
ansible-galaxy collection install kubernetes.core
ansible-galaxy collection install community.general
```

--------------------------------

### Event Processing Operator Deployment Example

Source: https://ibm.github.io/event-automation/ep/installing/installing-on-kubernetes

Example output showing a successfully deployed Event Processing operator, indicated by '1/1' in the READY column.

```text
NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
ibm-ep-operator                 1/1     1            1           1d2h
```

--------------------------------

### Example Patch Command for User Roles

Source: https://ibm.github.io/event-automation/eem/security/user-roles

An example of patching the user roles secret with specific Base64 encoded data for the 'quick-start-manager' instance.

```bash
kubectl patch secret quick-start-manager-ibm-eem-user-roles --type='json' -p='[{"op" : "replace" ,"path" : "/data/user-mapping.json" ,"value" : "ewogICJtYXBwaW5ncyI6IFsKICAgIHsKICAgICAgImlkIjogImF1dGhvcjEiLAogICAgICAicm9sZXMiOiBbCiAgICAgICAgImF1dGhvciIKICAgICAgXQogICAgfSwKICAgIHsKICAgICAgImlkIjogInZpZXdlcjEiLAogICAgICAicm9sZXMiOiBbCiAgICAgICAgInZpZXdlciIKICAgICAgXQogICAgfQogIF0KfQo='}]'
```

--------------------------------

### Example config.yaml for Event Processing UI

Source: https://ibm.github.io/event-automation/ep/advanced/deploying-customized

This is an example `config.yaml` file exported from the Event Processing UI, showing source and sink configurations for Kafka connectors.

```yaml
config:
  source:
    source___TABLE:
      properties.sasl.jaas.config: org.apache.kafka.common.security.scram.ScramLoginModule
        required username="<username_redacted>" password="<password_redacted>";
      connector: kafka
      format: json
      json.ignore-parse-errors: 'true'
      properties.bootstrap.servers: kafka.01:9002
      properties.isolation.level: read_committed
      properties.sasl.mechanism: SCRAM-SHA-512
      properties.security.protocol: SASL_SSL
      properties.ssl.endpoint.identification.algorithm: ''
      properties.ssl.truststore.certificates: '-----BEGIN CERTIFICATE----- [...] -----END CERTIFICATE-----'
      properties.ssl.truststore.type: PEM
      properties.tls.pemChainIncluded: 'false'
      scan.startup.mode: earliest-offset
      topic: input-topic
  sink_1:
    sink_1:
      properties.sasl.jaas.config: org.apache.kafka.common.security.scram.ScramLoginModule
        required username="<username_redacted>" password="<password_redacted>";
      connector: kafka
      format: json
      properties.bootstrap.servers: kafka.01:9002
      properties.sasl.mechanism: SCRAM-SHA-512
      properties.security.protocol: SASL_SSL
      properties.ssl.endpoint.identification.algorithm: ''
      properties.ssl.truststore.certificates: '-----BEGIN CERTIFICATE----- [...] -----END CERTIFICATE-----'
      properties.ssl.truststore.type: PEM
      properties.tls.pemChainIncluded: 'false'
      topic: output-topic

```

--------------------------------

### Example User Info Response

Source: https://ibm.github.io/event-automation/eem/security/groups

An example response from the `/auth/protected/userinfo` endpoint, illustrating the structure of user attributes. This helps in determining the correct path for the `userGroupClaimPointer`.

```json
{
  ...
  "attributes": {
    "idToken": {
      "data": {
        "roles": ["my-role"]
      }
    },
    "accessToken": {
      "groups": ["my-group"]
    },
    "userInfo": {
      "meta": {
        "organization": "hr"
      }
    }
  }
}
```

--------------------------------

### Example 200 Response for Reading an Option (v2+json)

Source: https://ibm.github.io/event-automation/eem-api-117

This is an example of a successful response when reading an option with the 'application/vnd.ibm.eem.v2+json' media type. It includes detailed information about the option and its controls.

```json
{
  "id": "string",
  "owner": "string",
  "organization": "string",
  "eventSourceId": "string",
  "alias": "string",
  "name": "string",
  "description": "string",
  "gatewayGroups": [
    "string"
  ],
  "hidden": true,
  "allowSubscriptions": true,
  "controls": [
    {
      "id": "string",
      "type": "approval",
      "requests": [
        {
          "id": "string",
          "owner": "string",
          "lastUpdated": 0,
          "status": "pending",
          "description": "string",
          "contact": "string",
          "outcome": "string",
          "subscriptionId": "string",
          "applicationId": "string"
        }
      ]
    }
  ],
  "groupVisibility": [
    "string"
  ]
}
```

--------------------------------

### Create PostgreSQL Database

Source: https://ibm.github.io/event-automation/tutorials/guided/tutorial-0

Set up a PostgreSQL database for the tutorials. This requires accepting the license, providing an entitlement key, and specifying the namespace. A default storage class is required.

```yaml
ansible-playbook \
    -e license_accept=true \
    -e ibm_entitlement_key=YOUR-ENTITLEMENT-KEY \
    -e eventautomation_namespace=event-automation \
    install/supporting-demo-resources/pgsql/install.yaml
```

--------------------------------

### Deploy Tutorial Environment

Source: https://ibm.github.io/event-automation/tutorials/guided/tutorial-0

Deploys the IBM Event Automation tutorial environment using an Ansible playbook. Ensure you accept the license and provide your entitlement key.

```ansible
ansible-playbook \
    -e license_accept=<true if you accept the IBM EA license> \
    -e install_certmgr=<true if you need a certificate manager> \
    -e ibm_entitlement_key=<your Entitled Registry key> \
    -e eventautomation_namespace=event-automation \
    install/event-automation.yaml
```

--------------------------------

### Populate Event Automation Catalog

Source: https://ibm.github.io/event-automation/tutorials/guided/tutorial-0

Run this script to populate the catalog with documentation for tutorial topics. Requires an API access token and logged-in oc client.

```bash
./eem-seed/reset-all-data.sh event-automation <access-token>
```

--------------------------------

### Install Operator for Single Namespace Management

Source: https://ibm.github.io/event-automation/ep/installing/installing-on-kubernetes

Example command to install the operator for managing `FlinkDeployments` only within the specified namespace, without additional configurations.

```bash
helm install flink ibm-helm/ibm-eventautomation-flink-operator -n "my-flink"
```

--------------------------------

### Check ClusterServiceVersion (CSV) Status

Source: https://ibm.github.io/event-automation/eem/installing/installing

Use the `oc get csv` command to list installed operators and check the PHASE column for 'Succeeded', indicating a successful installation.

```bash
oc get csv
```

--------------------------------

### Create Project using CLI

Source: https://ibm.github.io/event-automation/eem/installing/installing

Use the `oc new-project` command to create a dedicated namespace for Event Endpoint Management. The description and display name arguments are optional.

```bash
oc new-project <project_name> --description="<description>" --display-name="<display name>"
```

--------------------------------

### Get Network Policies for a Namespace

Source: https://ibm.github.io/event-automation/eem/security/network-policies

Run this command to display the installed network policies for a specific namespace in your Kubernetes cluster.

```bash
kubectl get netpol -n <namespace>
```

--------------------------------

### Get Operator Versions using oc CLI

Source: https://ibm.github.io/event-automation/ep/installing/uninstalling

Run these commands to retrieve the current CSV version for your installed subscriptions. This helps in identifying the correct version to use for uninstallation.

```bash
oc get subscription ibm-eventprocessing -o yaml | grep currentCSV
oc get subscription ibm-eventautomation-flink -o yaml | grep currentCSV
```

--------------------------------

### Event Endpoint Management Custom Resource Configuration

Source: https://ibm.github.io/event-automation/eem/installing/installing-on-kubernetes

Example configuration for an Event Endpoint Management custom resource. Ensure `spec.license.accept` is true and other license fields are set correctly. Update storage and TLS fields as needed. The `endpoints[server].host` must start with 'eem.'

```yaml
apiVersion: events.ibm.com/v1beta1
kind: EventEndpointManagement
# ...
spec:
  manager:
    endpoints:
      - name: ui
        host: my-eem-ui.mycluster.com
      - name: gateway
        host: my-eem-gateway.mycluster.com
      - name: admin
        host: my-eem-admin.mycluster.com
      - name: server
        host: eem.my-eem-server.mycluster.com

```

--------------------------------

### Example Helm list output

Source: https://ibm.github.io/event-automation/ep/installing/upgrading

This is an example output from the `helm list` command, showing deployed releases and their associated chart versions. Look for the `CHART` column to identify your Event Processing version.

```text
NAME                      NAMESPACE  REVISION  UPDATED                                 STATUS   CHART                            APP VERSION    
ibm-eventautomation-flink ep         1         2026-02-20 11:49:52.565373278 +0000 UTC deployed ibm-eventautomation-flink-1.4.7  9963366-651feed
ibm-eventprocessing       ep         1         2026-02-20 11:49:27.221411789 +0000 UTC deployed ibm-eventprocessing-1.4.7        9963366-651feed
```

--------------------------------

### Install Operator with Webhook Disabled

Source: https://ibm.github.io/event-automation/ep/installing/installing-on-kubernetes

Use this command to install the operator while disabling the webhook component, which is necessary if Cert Manager is not installed.

```bash
helm install flink ibm-helm/ibm-eventautomation-flink-operator -n "my-flink" --set webhook.create=false
```

--------------------------------

### Install Flink Operator CRDs with Helm

Source: https://ibm.github.io/event-automation/ep/installing/offline

Install the Custom Resource Definitions for the IBM Operator for Apache Flink using Helm. This is a prerequisite for installing the operator itself.

```bash
helm install <release-name> ~/.ibm-pak/data/cases/ibm-eventautomation-flink/<case-version>/charts/ibm-eventautomation-flink-operator-crd-<case-version>.tgz -n <target-namespace>
```

--------------------------------

### Install Event Processing CRDs with Helm

Source: https://ibm.github.io/event-automation/ep/installing/offline

Install the Custom Resource Definitions for Event Processing using Helm. This step is necessary before installing the Event Processing operator.

```bash
helm install <release-name> ~/.ibm-pak/data/cases/ibm-eventprocessing/<case-version>/charts/ibm-ep-operator-crd-<case-version>.tgz -n <target-namespace>
```

--------------------------------

### Deploy Tutorial with Persistent Storage

Source: https://ibm.github.io/event-automation/tutorials/guided/tutorial-0

Deploys the IBM Event Automation tutorial environment with persistent storage configurations for Event Streams, Event Endpoint Management, and Event Processing. This is useful for deployments on IBM Cloud.

```ansible
ansible-playbook \
    -e license_accept=true \
    -e install_certmgr=true \
    -e ibm_entitlement_key=<your Entitled Registry key> \
    -e eventautomation_namespace=event-automation \
    -e eventstreams_storage_class=ibmc-block-gold \
    -e eventendpointmanagement_storage_class=ibmc-block-bronze \
    -e eventprocessing_storage_class=ibmc-block-bronze \
    install/event-automation.yaml
```

--------------------------------

### Install Event Endpoint Management Operator CRDs

Source: https://ibm.github.io/event-automation/eem/installing/installing-on-kubernetes

Install the Custom Resource Definitions (CRDs) for Event Endpoint Management before installing the operator. Replace `<release-name>` and `<namespace>` with your specific values.

```bash
helm install \
   <release-name> ibm-helm/ibm-eem-operator-crd \
   -n <namespace>
```

--------------------------------

### watsonx.ai Prompt Example Input

Source: https://ibm.github.io/event-automation/tutorials/analyze-reviews

Example input reviews provided in the Prompt Lab to demonstrate the expected format for review analysis. This helps in testing and refining the prompt.

```text
Love at First Wear! I was blown away by the comfort and style of these jeans. The fit is perfect, and the material is so soft. I've worn them nonstop since I got them!,  I was expecting more from these jeans. The material is thin and the style is too casual for my taste., These jeans are okay, but the fit is a bit loose. I'd recommend sizing down if   you're unsure.
```

--------------------------------

### Copy Example Image to Local Storage

Source: https://ibm.github.io/event-automation/ep/security/verifying-signature

Example of copying a specific Event Processing operator catalog image into local storage using skopeo. This creates a directory containing the image manifest and signature files.

```bash
mkdir images
skopeo copy docker://icr.io/cpopen/ibm-eventprocessing-operator-catalog:v1.5.2 dir:./images

```

--------------------------------

### Generate Mirror Manifests

Source: https://ibm.github.io/event-automation/eem/installing/offline

Run this command to generate the necessary manifest files for mirroring images. Replace `<target-registry>` with your internal container image registry.

```bash
kubectl ibm-pak generate mirror-manifests ibm-eventendpointmanagement <target-registry>
```

--------------------------------

### Example Kubernetes Service Definition

Source: https://ibm.github.io/event-automation/eem/installing/install-k8s-egw

An example of a generated Kubernetes Service definition for an Event Gateway deployment.

```yaml
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: null
  labels:
    app: grp1-gwy1
    gatewayGroup: grp1
    gatewayId: gw1
  name: grp1-gwy1
spec:
  ports:
  # should match what was configured on the gateway in EEM Manager
  - port: 8443
    protocol: TCP
    targetPort: 8443
  selector:
    app: grp1-gwy1
    gatewayGroup: grp1
    gatewayId: gw1
```

--------------------------------

### Install Operator Custom Resource Definitions (CRDs) with Helm

Source: https://ibm.github.io/event-automation/eem/installing/offline

Installs the operator's Custom Resource Definitions (CRDs) using the Helm CLI. This step is necessary before installing the operator itself. Replace `<release-name>` and `<case-version>` with appropriate values.

```bash
helm install <release-name> ~/.ibm-pak/data/cases/ibm-eventendpointmanagement/<case-version>/charts/ibm-eem-operator-crd-<case-version>.tgz -n <target-namespace>
```

--------------------------------

### Example Response for Listing Subscriptions

Source: https://ibm.github.io/event-automation/eem-api-117

This is an example of a successful (200 OK) response when listing subscriptions. It details the structure of a subscription object, including its ID, owner, entry IDs, organization, credentials, client ID, contact, and gateways.

```json
[
  {
    "id": "string",
    "owner": "string",
    "entryId": [
      "string"
    ],
    "organization": "string",
    "credentials": {
      "type": "NONE",
      "data": {
        "username": "string",
        "mechanism": "PLAIN",
        "subjectCommonName": "string",
        "subjectOrganization": "string",
        "subjectCountry": "string",
        "subjectStateOrProvince": "string",
        "subjectLocality": "string"
      }
    },
    "clientId": "string",
    "contact": "string",
    "gateways": [
      "string"
    ]
  }
]
```

--------------------------------

### Verify ibm-pak Installation

Source: https://ibm.github.io/event-automation/eem/installing/offline

Confirms that the `ibm-pak` plugin has been successfully installed and is accessible via the `kubectl ibm-pak` command.

```bash
kubectl ibm-pak --help
```

--------------------------------

### Create Cluster API Response Example

Source: https://ibm.github.io/event-automation/eem-api-117

Example of a successful response when creating a cluster, returning the cluster ID.

```json
{
  "id": "string"
}
```

--------------------------------

### Create OpenShift Project using CLI

Source: https://ibm.github.io/event-automation/ep/installing/installing

Use this command to create a new project (namespace) for Event Processing. Optional arguments can specify a description and display name.

```bash
oc new-project <project_name> --description="<description>" --display-name="<display_name>"
```

--------------------------------

### Example Flink Storage Configuration

Source: https://ibm.github.io/event-automation/ep/installing/planning

Example values for setting the STORAGE_CLASS and STORAGE_CAPACITY environment variables. Ensure the chosen storage class meets Flink's requirements.

```bash
export STORAGE_CLASS=rook-cephfs
export STORAGE_CAPACITY=20Gi
```

--------------------------------

### Example Join Condition with Time Window

Source: https://ibm.github.io/event-automation/ep/nodes/joins

An example of a join condition that includes a time window for matching events.

```sql
payment_stream.timestamp BETWEEN order_stream.timestamp AND order_stream.timestamp + INTERVAL '10' MINUTE
```

--------------------------------

### Copy Example UDF JAR

Source: https://ibm.github.io/event-automation/ep/advanced/deploying-production

Example of copying a specific UDF JAR file to the Flink lib directory.

```dockerfile
COPY --chown=flink:root /udfproject/target/udf.jar /opt/flink/lib
```

--------------------------------

### Switch to New OpenShift Project using CLI

Source: https://ibm.github.io/event-automation/ep/installing/installing

After creating a project, use this command to switch your current context to the newly created namespace.

```bash
oc project <new-project-name>
```

--------------------------------

### Install Required Packages on macOS

Source: https://ibm.github.io/event-automation/ep/installing/configuring

Install `gettext` and `openssl@3` using HomeBrew on macOS. This is a prerequisite for using OpenSSL commands.

```bash
brew install gettext openssl@3
```

--------------------------------

### Pull Image using Skopeo

Source: https://ibm.github.io/event-automation/eem/security/verifying-signature

Create a directory and use skopeo to pull the image into local storage. This downloads the image as files, including manifest and signature files.

```bash
mkdir images
skopeo copy docker://<imageName> dir:./images
```

```bash
mkdir images
skopeo copy docker://icr.io/cpopen/ibm-eventendpointmanagement-operator-catalog:11.7.4 dir:./images
```
Tokens:
Raw