Deploying the dashboard with a reverse proxy
Proxies are a common pattern in Kubernetes; there are proxies at every layer in a Kubernetes cluster. The proxy pattern is also used by most service mesh implementations on Kubernetes, creating sidecars that will intercept requests. The difference between the reverse proxy described here and these proxies is in their intent. Microservice proxies often do not carry a session, whereas web applications need a session to manage the state.
The following diagram shows the architecture of a Kubernetes Dashboard with a reverse proxy:
Figure 10.3: Kubernetes Dashboard with a reverse proxy
The reverse proxy shown in Figure 10.3 performs four roles:
- Routing: Each of the containers used by the dashboard has its own path off of the host URL. The reverse proxy is responsible for routing requests to the correct container.
- Authentication: The reverse proxy intercepts unauthenticated requests (or stale sessions) and triggers...
