enriched commented on issue #266: URL: https://github.com/apache/pulsar-manager/issues/266#issuecomment-641522334
Running into the same issue, using [Ambassador](https://www.getambassador.io/docs/latest/topics/using/rewrites/) with a helm templated service: ```yaml apiVersion: v1 kind: Service metadata: name: {{ .Release.Name }}-pulsar-manager-http annotations: getambassador.io/config: | apiVersion: ambassador/v1 kind: Mapping name: "{{ .Release.Name }}-pulsar-manager" prefix: /pulsar/ service: "{{ .Release.Name }}-pulsar-manager-http:9527" labels: app: pulsar cluster: {{ .Release.Name }}-pulsar component: pulsar-manager release: {{ .Release.Name }} spec: type: ClusterIP ports: - name: frontend port: 9527 protocol: TCP targetPort: 9527 selector: app: pulsar component: pulsar-manager release: {{ .Release.Name }} sessionAffinity: None ``` Running locally on Docker for Mac the request to http://localhost/pulsar/ responds with a 200 and html: ```html <!DOCTYPE html> <html> <head> <meta charset=utf-8> <meta http-equiv=X-UA-Compatible content="IE=edge,chrome=1"> <meta name=renderer content=webkit> <meta name=viewport content="width=device-width,initial-scale=1,maximum-scale=1,user-scalable=no"> <title>Pulsar Admin UI</title> <link rel="shortcut icon" href=/favicon.ico> <link href=/static/css/chunk-elementUI.31757218.css rel=stylesheet> <link href=/static/css/chunk-libs.bd17d456.css rel=stylesheet> <link href=/static/css/app.b2eade8f.css rel=stylesheet> </head> <body> <div id=app></div> <script>redacted for brevity</script> <script src=/static/js/chunk-elementUI.ab5927a0.js></script> <script src=/static/js/chunk-libs.1395be8a.js></script> <script src=/static/js/app.1ecd3f65.js></script> </body> </html> ``` requests to get stylesheets and scripts under the `/static/` all go to `localhost/static/...` and return 404 rather than `localhost/pulsar/static/...` where I would expect them to be able to find the resources. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
