Can't access evenstore-admin portal if cluster size greater than 1 (GKE)

[TomBalt]

**Is this a BUG REPORT ** :

Version of Helm and Kubernetes:
Client: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}

GKE 1.13.7-gke.8

Which chart:
helm eventstore-0.2.3

What happened:
Can't access evenstore-admin portal, if cluster size greater than 1 (GKE) using port-forward on kubernetes.
I have installed cluster with a size of 3 and used port-forward function to reach admin portal using localhost url and it doesn't work. It comes back as url of one of the EventStore node's pod IP.
If I deploy EventStore with cluster size set to 1, it works just fine, I can reach admin portal.

What you expected to happen:
I would expect to have an url still localhost and be able to reach via localhost url after running command "kubectl port-forward svc/eventstore-admin 2113 -n eventstore".

How to reproduce it (as minimally and precisely as possible):
helm install --name eventstore --namespace eventstore eventstore/eventstore --set 'clustersize=3'
kubectl port-forward svc/eventstore-admin 2113 -n eventstore
Try to reach evenstore-admin portal using url -> http://localhost:2113

Anything else we need to know:

[andymeierdev]

Unfortunately it is difficult to port forward with a cluster and I have not been able to figure out a way to get it to work out of the box.

A work around is to use a tool like telepresence. See this note https://github.com/EventStore/EventStore.Charts/blob/master/stable/eventstore/templates/NOTES.txt#L22

Here is article which is related https://medium.com/@valercara/connecting-to-a-kafka-cluster-running-in-kubernetes-7601ae3a87d6

[TomBalt]

@ameier38 Thank you for coming back.

I had a look to telepresence tool and tried to replace "eventstore-admin" deployment with local one. This way I should have an access via local URL, however it doesn't work... Another thing is it a right way to access admin portal? Would it effect clusters functionality if it's running locally?

Have you managed to make it work with telepresence? If you did, could you share your insights?

Much appreciated.
T.

[andymeierdev]

@TomBalt I was thinking you could use telepresence to access the admin UI but really it can only be used to connect to the cluster since the browser requests are not being proxied.

I am trying to come up with a solution as I would really like this feature as well. I need to do a bit more work on figuring out the correct way to set up the networking. I am tracking here kurrent-io/KurrentDB#1984