Service mesh doesn't show topology

[yb172]

load-generator sends request to gen-gateway which talks to either gen-number, gen-word, or gen-internets. However that's what topology shows:

[yb172]

Interestingly enough linkerd routes svc/gen-gateway -n gen gives nothing - says service profile not found

[yb172]

Output of tap command suggested in "troubleshooting" section:

$ linkerd tap deploy/gen-gateway -o wide -n gen | grep req
req id=132:53 proxy=out src=10.36.0.46:59448 dst=10.39.254.147:10000 tls=no_identity :method=POST :authority=10.39.254.147:10000 :path=/wordgen.InternetsWordGenerator/GetWord src_res=deploy/gen-gateway src_ns=gen
req id=132:54 proxy=out src=10.36.0.46:59458 dst=10.39.254.147:10000 tls=no_identity :method=POST :authority=10.39.254.147:10000 :path=/wordgen.InternetsWordGenerator/GetWord src_res=deploy/gen-gateway src_ns=gen
req id=132:55 proxy=out src=10.36.0.46:38484 dst=10.39.240.160:10000 tls=no_identity :method=POST :authority=10.39.240.160:10000 :path=/wordgen.WordGenerator/GenerateWord src_res=deploy/gen-gateway src_ns=gen

Looks like paths are there, but authority header contains ips...

[yb172]

And it looks like this is caused by the way I'm doing service discovery: https://github.com/yb172/experiments/blob/master/kube/testtools/config.yaml#L4