Cloud Pak for Integration

 View Only

Managing CP4I Dev & Test Environment in Non-Production Cluster

  • 1.  Managing CP4I Dev & Test Environment in Non-Production Cluster

    Posted Thu September 29, 2022 03:21 PM
    Hello All,
    My customer wants to manage Dev environment besides Test environment. I wanted to apply the best and affordable approach to provide the customer request and researched the possibilities. 
    The first option to manage the new environment is placing it in non-production cluster because of the infrastructure cost and management efforts. Other option can be managing the DEV environment in a separate cluster If the customer has budget and critical applications which run on cp4i. 

    When I choose the first option, I can isolate the environments by managing the dev and test instance in separate platform ui. 
    In my case, applying the option is  challenging because operators of cp4i were installed with cluster-wide scope in non-production cluster and instances (MQ, app connect, api connect) were cerated on platform-ui.  Nevertheless I decided to convert cluster-wide operators to namespace-scope. I applied the procedure on my environment first and then checked it with support and dev team.

    So converting operator scope is possible If you deploy the platform navigator in same namespaces with your instances.  When you uninstall the cluster-wide operators , the instances you created before continue running. If you reinstall the operators to the namespace where your instance are running, the instances can automatically relates to the operators.

    ------------------------------
    Basak Yazirli
    ------------------------------