Add proxy/ingress/gateway to Mirror Node and provide ability for user to pass in a reserved static IP address #929
Labels
HashSphere Requirement
Needs Refinement
The issue needs more refinement and/or design before it can be worked
P0
An issue impacting production environments or impacting multiple releases or multiple individuals.
It appears that the current mirror node deployment is deployed without a proxy, ingress, or gateway. It has the ability to leverage Traefik, but I believe that is overkill. The ask is that we have solo deploy a proxy, ingress, or gateway to sit in front of all of the services it offers. I believe looking at their charts that they are configured to handle a gateway.
Additionally, we need to have a flag in solo to provide the reserved static IP address to use when deploying it to a cloud service that supports it.
The text was updated successfully, but these errors were encountered: