Deploy IBM Sterling Connect:Direct on OpenShift using Ansible Scripts

Playbook will run the last version of Connect:Direct, but take care of Kubernetes/Openshift version is supported

Connect:Direct helm-chart Kubernetes OpenShift Helm
6.3.0.3_ifix012 1.3.10 >=1.24.0 <1.30.0 >= 4.11 and <= 4.16 >= 3.14.x
6.3.0.3_ifix009 1.3.9
6.3.0.3_ifix003 1.3.8

Check with

kubectl version

Preparation

1. IBM Entitled Registry

You must have kubectl, oc, git and ansible installed in your machine

Log in the IBM Container software library with the IBMid and password that are associated with the entitled software. Click Get entitlement key. With key export variable

export ENTITLED_REGISTRY_KEY=<entitlement_key>

2. Login on OpenShift

Do a login in Openshift console and run the command:

oc login --token=sha256~P...k --server=https://c....containers.cloud.xxx.com:31234

3. Cloning ansible-ibm-websphere from git

git clone https://github.com/ibm-sterling-devops/ansible-ibm-sterling.git

4. Set roles path

To run playbook the playbook

cd ansible-ibm-sterling

export ANSIBLE_CONFIG=./ansible.cfg

Deploy you Connect:Direct

1) Define C:D node name

export CD_NODENAME=CDNODE01

2) To run the playbook

ansible-playbook playbooks/deploy_cd.yml

check for sterling-cdnode01-dev namespace. The C:D node name will be CDNODE01

Examples

Example 1: Change namespace and C:D node name

To change namespace/project and C:D node name

cd ansible-ibm-sterling

export CD_NAMESPACE=sterling-cdcompany01-prod
export CD_NODENAME=COMPANY01

ansible-playbook playbooks/deploy_cd.yml

Environment Variable

For all environment variables