Support .eth in browser

Problem to be solved

I wanted to load eternalsafe, the simple gnosis multisig fork.

However, to pull it from ipfs i needed to use something like eth.limo

It would be great if i could run eternalsafe without a centralised third party dependency

Proposed solution

Install an ipfs light client (?)

Set 127.0.0.1 .eth or equivalent in /etc/hosts. This routes .eth domain names to the stack when running in --host mode.

Create an ingress that matches *.eth or similar.

Route that to a service+pod that fetches this ens info, and potentially fetches from ipfs. (Might need https://github.com/ensdomains/ensjs/tree/main/docs/basics).

Serve the returned html on that route.

All going to plan, that would allow you to write eternalsafe.eth into your browser, and pull the UI without anything but p2p.

The issue names no files or tests; start by reviewing the repository's Kubernetes deployment configuration and the proposed ingress, service, and pod flow. Research how ENS resolution and IPFS retrieval would fit the stack, and define done as loading an .eth site in a browser without the centralized gateway dependency.