SPIKE - Identify how default Big Bang configuration could deploy two ingress gateways
Currently Big Bang deploys with a single ingress gateway and examples on how to deploy a second gateway. This can cause inexperienced users to deploy administrative tools (e.g. Prometheus, Grafana, Elasticsearch) on a publicly accessible ingress. Some of these may be insecure (e.g. Prometheus).
For Big Bang, we should find a way to default to a public and private ingress gateway. The user should still be able to disable the private gateway (and all apps would default to the public one). But providing a two gateway solution is a best practice that should be provided out of the box.
This spike is to create a proof of concept that works with two gateways by default. The solution needs to have an easy option to deploy on k3d without metallb (e.g. disable the second gateway and everything works). Lastly, the researcher should identify which apps should default to the public vs. private gateways.