[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[x] Chart Version bumped
[x] Chart packaged and index updated (you can use ./release)
[x] CHANGELOG.md updated
[x] Variables and other changes are documented in the README.md
What this PR does / why we need it:
Allows user to forward a local port in order to connect to the cluster
This only works for a single node unless tools like telepresence are used.
Which issue this PR fixes(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #29
Special notes for your reviewer:
In order to forward a local port we need to bind the pod to 0.0.0.0. If we have more than one node however, this causes an issue when trying to connect using discover://host:2113. We can fix this by setting the EVENTSTORE_EXT_IP_ADVERTISE_AS to the pod ip address. This causes an issue with accessing the admin interface though so we should not advertise the address when there is only 1 node.
So that port forwarding works out of box I think it is better to set the default clusterSize=1.
PR Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
./release)What this PR does / why we need it: Allows user to forward a local port in order to connect to the cluster
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #29Special notes for your reviewer: In order to forward a local port we need to bind the pod to 0.0.0.0. If we have more than one node however, this causes an issue when trying to connect using
discover://host:2113. We can fix this by setting theEVENTSTORE_EXT_IP_ADVERTISE_ASto the pod ip address. This causes an issue with accessing the admin interface though so we should not advertise the address when there is only 1 node.So that port forwarding works out of box I think it is better to set the default
clusterSize=1.Resources