Uploaded image for project: 'Multicloud'
  1. Multicloud
  2. MULTICLOUD-820

Unify Multicloud-k8s endpoint URL published via MSB

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Medium Medium
    • None
    • None
    • MULTICLOUD-K8S

      Current multicloud-k8s endpoint configured in MSB is rooted at /, therefore all communication to this service requires doubled version path in URI (as MSB also adds it's versioning). Example url looks like: http://MSB_NODE_IP:MSB_PORT/api/multicloud-k8s/v1/v1/rb/definition/test-rbdef/1/profile

      Fixing this would enable communicating with mc-k8s via normalized URL (http://MSB_NODE_IP:MSB_PORT/api/multicloud-k8s/v1/rb/definition/...) but such change would be backward incompatible, so one would need to ensure all other components that communicate with mc-k8s via MSB use correct, new path.
      As far as I understand, in general, mc-k8s should be always proxied by multicloud broker, so actually only Robot and/or Human operator may be in need of using MSB? I mean the desired state, not current one.
      As of now, I'm aware only of Robot, that uses MSB (in healthcheck script), but some more detailed code search would need to be done. Also documentation would need to be updated as well.
      https://gerrit.onap.org/r/gitweb?hb=refs/heads/master;a=blob;p=integration.git;f=docs/docs_vfw_edgex_k8s.rst
      https://gerrit.onap.org/r/gitweb?hb=refs/heads/master;a=blob;p=testsuite.git;f=robot/testsuites/health-check.robot#l121

            kbanka kbanka
            kbanka kbanka
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: