Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1119

[Templates] remove Smart Router port/protocol configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.1.GA
    • None
    • Deployment
    • Compatibility/Configuration
    • Hide
      1. Process the template rhpam70-prod.yaml or rhpam70-sit.yaml as follows
        oc process -f templates/rhpam70-sit.yaml -p MAVEN_REPO_URL=http://maven.example.com -p MAVEN_REPO_USERNAME=mvn -p MAVEN_REPO_PASSWORD=pwd -p BUSINESS_CENTRAL_HTTPS_SECRET=bcsecret -p KIE_SERVER_HTTPS_SECRET=kssecret -p KIE_SERVER_ROUTER_PORT=9999
        | grep -e 9000|9999 -A 4 -B 4
        
      1. Confirm port 9999 is set as env variable to Smart Rotuer and BCMonitoring Deployment configs
        {
           "name": "KIE_SERVER_ROUTER_PORT",
            "value": "9999"
        },
        
      2. Confirm port 9000 is still exposed in the Deployment Config and used in the service
        "spec": {
          "ports": [
             {
                "port": 9000,
                "targetPort": 9000
             }
           ],
        ...
         "ports": [
            {
                "containerPort": 9000,
                "name": "http",
                "protocol": "TCP"
            }
        
      Show
      Process the template rhpam70-prod.yaml or rhpam70-sit.yaml as follows oc process -f templates/rhpam70-sit.yaml -p MAVEN_REPO_URL=http: //maven.example.com -p MAVEN_REPO_USERNAME=mvn -p MAVEN_REPO_PASSWORD=pwd -p BUSINESS_CENTRAL_HTTPS_SECRET=bcsecret -p KIE_SERVER_HTTPS_SECRET=kssecret -p KIE_SERVER_ROUTER_PORT=9999 | grep -e 9000|9999 -A 4 -B 4 Confirm port 9999 is set as env variable to Smart Rotuer and BCMonitoring Deployment configs { "name" : "KIE_SERVER_ROUTER_PORT" , "value" : "9999" }, Confirm port 9000 is still exposed in the Deployment Config and used in the service "spec" : { "ports" : [ { "port" : 9000, "targetPort" : 9000 } ], ... "ports" : [ { "containerPort" : 9000, "name" : "http" , "protocol" : "TCP" }

      The production and sit templates allow configuring the Smart Router port and protocol. This will be set to the Business Central Monitoring deployment config:

      Business Central Monitoring Deployment config
                - name: KIE_SERVER_ROUTER_SERVICE
                  value: "${APPLICATION_NAME}-smartrouter"
                - name: KIE_SERVER_ROUTER_PORT
                  value: "${KIE_SERVER_ROUTER_PORT}"
                - name: KIE_SERVER_ROUTER_PROTOCOL
                  value: "${KIE_SERVER_ROUTER_PROTOCOL}"
      

      If a user chooses a different value, the configuration won't work as only the port 9000 and HTTP protocol are exposed in the Smart Router's DeploymentConfig. They can't be changed.

      Smart Router Deployment Config
                ports:
                - name: http
                  containerPort: 9000
                  protocol: TCP
      

      Smart router is accessed by the service which is also configured to port 9000

      Smart Router service
      - kind: Service
        apiVersion: v1
        spec:
          ports:
          - port: 9000
            targetPort: 9000
          selector:
            deploymentConfig: "${APPLICATION_NAME}-smartrouter"
      

            rhn-support-rromerom Ruben Romero Montes
            rhn-support-rromerom Ruben Romero Montes
            Karel Suta Karel Suta
            Karel Suta Karel Suta
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: