Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-8045

Provide custom proxy path for dynamic plugins

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • 2
    • False
    • False
    • ?
    • No
    • ?
    • ?
    • ?
    • HAC Infra - Sprint 211, HAC Infra - Sprint 213

      Dynamic plugins must access proxies using the namespace, name, and port of proxied services, in the following format:

      /api/proxy/namespace/<namespace>/service/<name>:<port>

       

      Because these values might only be known at installation time, it would be helpful to be able to access these proxies via an alias or path that could be fixed. For example, if the ConsolePlugin was specified as follows:

      apiVersion: console.openshift.io/v1alpha1
      kind: ConsolePlugin
      metadata:
        name: acm-console-plugin
      spec:
        displayName: Red Hat Advanced Cluster Management
        proxy:
          services:
            - authorize: true
              name: console-chart-9bc0f-console-v2
              namespace: open-cluster-management
              port: 3000
              path: acm-proxy
        service:
          basePath: /plugin/
          name: console-chart-9bc0f-console-v2
          namespace: open-cluster-management
          port: 3000 

      Then the proxy could be accessed via:

      /api/proxy/<plugin-name>/<proxy-path> ie. /api/proxy/acm-console-plugin/acm-proxy

            jhadvig@redhat.com Jakub Hadvig
            rh-ee-kcormier Kevin Cormier
            YaDan Pei YaDan Pei
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: