Skip to content

Latest commit

 

History

History
78 lines (57 loc) · 2.69 KB

cp4ba-baw-recipe.md

File metadata and controls

78 lines (57 loc) · 2.69 KB
Raw

Deploy Business Automation Workflow

This recipe is for deploying the the STARTER deployment of Business Automation Workflow assuming you reserved a GitOps Cluster.

Multi-tenancy-gitops-services - Kustomization.yaml

  1. Edit the kustomization file multi-tenancy-gitops-services/operators/ibm-cp4ba-operator/kustomization.yaml, and un-comment, comment, commit, and push the following changes:
resources:
#- deployment/cp4ba-catalogsource.yaml      # comment this out
#- deployment/cp4ba-subscription.yaml       # comment this out

### BAW DEPLOYMENT ###
- deployment/cp4ba-baw-catalogsource.yaml
- deployment/cp4ba-baw-subscription.yaml

Infrastructure - Kustomization.yaml

  1. Edit the Infrastructure layer ${GITOPS_PROFILE}/1-infra/kustomization.yaml, un-comment the following lines, commit and push the changes. Then refresh the infra Application in the ArgoCD console.
- argocd/consolenotification.yaml
- argocd/namespace-tools.yaml
- argocd/namespace-ibm-common-services.yaml
- argocd/namespace-cp4ba.yaml
- argocd/serviceaccounts-baw.yaml
- argocd/machine-configuration.yaml

💡 NOTE
*** make sure to add, commit & push the changes into git. ***

Services - Kustomization.yaml

  1. Add IBM ENTITLEMENT KEY on cp4ba & ibm-common-services namespaces using the terminal.

💡 NOTE
*** make sure you are logged into your cluster in your terminal and you change . ***

oc create secret docker-registry ibm-entitlement-key -n cp4ba \
--docker-username=cp \
--docker-password=<ENTITLEMENT-KEY> \
--docker-server=cp.icr.io
oc create secret docker-registry ibm-entitlement-key -n ibm-common-services \
--docker-username=cp \
--docker-password=<ENTITLEMENT-KEY> \
--docker-server=cp.icr.io

  1. Edit the Services layer ${GITOPS_PROFILE}/2-services/kustomization.yaml and install CP4BA operator and BAW instance by uncommenting the following lines:

    ## IBM CP4BA operator
- argocd/operators/ibm-cp4ba-operator.yaml

    💡 NOTE
    *** make sure to add, commit & push these changes to git. Then make sure it has finished deploying in argocd console before un-commenting the next step. ***

    - argocd/instances/ibm-cp4ba-baw.yaml

💡 NOTE
*** make sure to add, commit & push the changes into git. The overall process took around 2.5 hours ***

Validation

  1. Verify the status: 
    oc get icp4acluster icp4adeploy -n cp4ba -o jsonpath="{.status}{'\n'}" | jq