Installation

Requirements link

• OpenShift® Cluster (version 4.10 or later)

• OpenShift® Command Line Interface (CLI)

• Ansible® CLI Tools (version 2.9.10 or later)

  Ensure you’ve installed Ansible correctly by restarting your terminal and running:

    ansible --version
    

• Kubernetes Python Client

• z/OS Cloud Broker v2.2.0+

• z/OS Cloud Broker Encryption CLI (optional)

Installation link

The IBM Operator Collection SDK can be installed from Ansible® Galaxy, directly from GitHub, or via a docker image stored in the IBM Cloud Container Registry

  ansible-galaxy collection install ibm.operator_collection_sdk
  

  ansible-galaxy collection install git+https://github.com/IBM/operator-collection-sdk.git#ibm/operator_collection_sdk -f
  

  mkdir -vp operator-collection-sdk/
oc image extract icr.io/zmodstack/operator-collection-sdk:latest --path /:operator-collection-sdk/ --confirm
ansible-galaxy collection install ./operator-collection-sdk/ibm/operator_collection_sdk -f
  

Upgrading link

Supply the --upgrade flag to upgrade the collection, e.g.

  ansible-galaxy collection install ibm.operator_collection_sdk --upgrade
  

Setup link

The following steps are required prior to deploying your Operator in OpenShift® using the IBM Operator Collection SDK playbooks:

1. Install the z/OS Cloud Broker Operator in your namespace and create an instance of ZosCloudBroker.
2. Log into the OpenShift cluster from the command line and run the oc project command to navigate to the project where the z/OS Cloud Broker Operator is installed.

Experiencing Issues? link

Submit an issue