Closed blairdrummond closed 2 years ago
Note: for applications that believe X-Forwarded-Proto: https
request header as an indication that HTTPS was used and terminated somewhere, @rohank07 did this with an Istio Virtual Service for our Trino implementation.
Changes outlined in README in v2-alpha
branch of aws js explorer fork https://github.com/StatCan/aws-js-s3-explorer/tree/v2-alpha.
Associated K8s manifests are in https://github.com/Collinbrown95/kind-blob-csi-mock-aaw/tree/%40cbrown/s3proxy-ui.
(transferred from another issue)
@Collinbrown95 I'd like your input on this!
I have a basic UI running. It's just 3 html+css+js files as a configmap in an nginx container.
There are a few things we should look at:
Anything else you can think of? You'll notice I made the nginx sidecar (which serves the frontend) serve the assets under
/s3/
. I think we could do this or something similar to make the UI work with the Kubeflow central dashboard virtual service thing, similarly to how we did it with gitea.There is a separate issue for the central dashboard thing, but we may need to configure the services and nginx config.