We had the deployed dashboard connecting to the kinto-core API through the public network. (e.g. https://core.kinto.somedomain.com)
But for the case if we want to do port-forwarding, we have to forward both dashboard and the core
Here the idea is to do a reverse proxy inside the dashboard container, which forwards the connection to core through internal k8s connection (i.e. pod to pod connection via http://kinto-core:8090), and expose the proxy via /api/*
So if we do port-forwarding, we can expose only the dashboard and without any modifications to any env vars as we always connect to /api
solving this
We had the deployed dashboard connecting to the kinto-core API through the public network. (e.g. https://core.kinto.somedomain.com) But for the case if we want to do port-forwarding, we have to forward both dashboard and the core
Here the idea is to do a reverse proxy inside the dashboard container, which forwards the connection to core through internal k8s connection (i.e. pod to pod connection via http://kinto-core:8090), and expose the proxy via
/api/*So if we do port-forwarding, we can expose only the dashboard and without any modifications to any env vars as we always connect to
/api