FR: Cloud - Make certain ports publicly accessible with dynamic DNS records

[barnabasbusa]

Background & motivation

Currently if a new EIP needs to be tested, a whole bunch of tooling and repositories have to be deployed. If kurtosis cloud could offer a way to run medium term (about 2-3weeks) long testing locations, it would enable us to use it for one off EIP testing playground.

For this, it would be essential to be able to be able to reach certain clusters publicly. This doesn't mean to need to make all ports public, but rather specific ones (selected by the user that creates a new enclave).

Desired behaviour

• Create a new enclave
• Spin up ethereum-package
• Create a public port mapping for - map it to a unique DNS record
  • Example 1 : Create a public port mapping for el-1-geth-lodestar port 8545 - map it to rpc.kurtosis-enclave-name.kurtosis.tech
  • Example 2: Create a port mapping to dora.
• Create a DNS record automatically to this host.
• Add optional basic authentication header support (optional for v1)
• Allow anyone to add given DNS to their metamask and use it as an rpc endpoint/ or anyone to browse Dora instance.

How important is this to you?

Painful; the lack of this feature makes using Kurtosis frictionful.

What area of the product does this pertain to?

Frontend: the Graphical User Interface, including the Enclave Manager

[barnabasbusa]

Thanks to @h4ck3rk3y this is now implemented.