bschurig commented 4 years ago

Is this a request for help?: No

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature Request

Version of Helm and Kubernetes:

Which chart: Eventstore

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

bschurig commented 4 years ago

Not sure where my requests went, but

We have a use case at our company for needing to access the Eventstore cluster from outside of a kubernetes cluster. The changes would be relatively trivial - updating the Eventstore service templating so that you can run it as a NodePort with ExternalTrafficPolicy set to local. It would also be helpful to have the ability to add annotations to the services so that services like External-DNS can be leveraged and have an ingress to access the admin UI.

Are there any plans to update the chart to include these changes or something similar? If not, I'd be happy to open a pull request if you're open to the requested changes.

01100010011001010110010101110000 commented 4 years ago

I believe #40 would fix this, though it would be nice to make it include the rewrite rule from #45

bschurig commented 4 years ago

40 would fix the ingress issue, #45 would be helpful as well. Is there any interest in making the eventstore service in addition to the admin UI accessible from outside the Kubernetes cluster that it's running in?

HassanHashemi commented 4 years ago

Any news on this one?

EventStore / EventStore.Charts

Update eventstore chart to allow access external to cluster, add ingress for admin service #47

Is this a request for help?: No

40 would fix the ingress issue, #45 would be helpful as well. Is there any interest in making the eventstore service in addition to the admin UI accessible from outside the Kubernetes cluster that it's running in?