feat: HTTP traffic should be routable to the user services using more than one Host header format

[laurentluce]

Background & motivation

The request Host header reaching the user service should match the original request Host header so URLs generation and redirects work correctly. This should happen locally and in the cloud.

Desired behaviour

Traefik routes http traffic to the user services. The user service Host header label should accept the following two formats:

• <port number>.<service short uuid>.<enclave short uuid>
• <port number>.<service short uuid>.<enclave short uuid>.<cloud instance short uuid>.<subdomain>

Method to update:

kurtosis/container-engine-lib/lib/backend_impls/docker/object_attributes_provider/enclave_object_attributes_provider.go

Line 533 in c640c5e

func (provider *dockerEnclaveObjectAttributesProviderImpl) getTraefikLabelsForEnclaveObject(serviceUuid string, ports map[string]*port_spec.PortSpec) (map[*docker_label_key.DockerLabelKey]*docker_label_value.DockerLabelValue, error) {

How important is this to you?

Critical; Kurtosis is unusable for me without it.

What area of the product does this pertain to?

Other: anything not covered by the above

[leoporoli]

It was fixed with those PRs, and it supports retro-compatibility.

[daramir]

@leoporoli was this tested?
I'm not sure if the Traefik Golang Regexp for Host matching

HostRegexp(`{^name:%d-%s-%s-?%s$}`)

is correct?

Is the caret in ^name part of the "arbitrarily named variable followed by the colon-separated regular expression"?

I have a kurtosis setup running on docker that I would like to use the reverse proxy feature for, but it's unusable... I'm unable to reach those hosts on the Traefik configured routes.