As part of the Superset on Kubernetes migration, we have created a single container definition for superset in T352165: Create a superset container image using the PipelineLib framework.
Whilst this has been shown to work during our testing, it struck us that it's not very efficient to use gunicorn workers to serve static page content.
A more efficient method would be to create separate containers for the front-end and back-end components.
We could then use a dedicated webserver to serve the static assets and route the traffic to the correct container from the envoy level.
This approach would give us greater capacity and scalability. It might also work well as a means of solving: T356490: [superset-k8s] Find a solution for the requestctl-generator html page
