Uploaded image for project: 'CORD'
  1. CORD
  2. CORD-2987

Design and implement replacement for old Apache proxy in K8S

    XMLWordPrintable

    Details

    • Type: Task
    • Status: To Do (View Workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Kubernetes, XOS
    • Labels:
      None
    • Story Points:
      5

      Description

      According to Zack Williams:

      ****

      Definately need proxy for: GUI, TOSCA, WS, Chameleon.

      The previous pod had apache proxy in front of the XOS gui, chameleon, ONOS, MaaS, and other containers/services. It seems like that should be handled natively in k8s.

      ****

      The right pattern to replace the traditional proxy in kubernetes is a kubernetes ingress controller. There is an NGINX based ingress controller that we get out of the box that we can use: https://kubernetes.io/docs/concepts/services-networking/ingress/ and https://github.com/kubernetes/ingress-nginx.

      We need to design and implement the nginx proxy ingress to replace the apache proxy.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            gopinath Gopinath Taget (Inactive)
            Reporter:
            gopinath Gopinath Taget (Inactive)
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Gerrit Reviews

                There are no open Gerrit changes