Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-3516

Expose Kogito services on default HTTP port instead of 8080

XMLWordPrintable

    • False
    • False
    • Undefined
    • ---
    • ---
    • 2020 Week 40-42 (from Sep 28)

      Today we expose the Kubernetes Service port in 8080, the same one as the container. Would be easier to integrate with other platforms to just expose the service at 80, so a simple call to the Kubernetes generated DNS would do.

      So instead of :

      spec:
        clusterIP: 10.110.100.253
        ports:
        - name: http
          port: 8080
          protocol: TCP
          targetPort: 8080
        selector:
          app: pr-checker-workflow
        sessionAffinity: None
        type: ClusterIP
      status:
        loadBalancer: {}
      

      We would have:

      spec:
        clusterIP: 10.110.100.253
        ports:
        - name: http
          port: 80
          protocol: TCP
          targetPort: 8080
        selector:
          app: pr-checker-workflow
        sessionAffinity: None
        type: ClusterIP
      status:
        loadBalancer: {}
      

      See the port attribute.

              rhn-support-zanini Ricardo Zanini
              rhn-support-zanini Ricardo Zanini
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: