You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This tool has been super useful! Feature request: It'd be nice if there was a way to generate the same, unique port for each pod every time. I'm using a StatefulSet with 5 replicas and would like to guarantee that pod-0 through pod-5 always get the same unique port. I don't really care what the external ports are, as long as they stay the same.
The text was updated successfully, but these errors were encountered:
Interesting use case, I assume that your client software cannot handle dynamic ports?
In general, I think your idea is possible.
The tool just needs to allocate the Service and add an internal annotation to the StatefulSet.
When new pods are created, this tool takes a free Service and assigns the Endpoint to the pod.
I am not quite sure how rolling upgrades behave and if there is the possibility of more than 5 (your example) nodes running at the same time.
Unfortunately, I don't have time to implement such a feature current.
It's just a nice-to-have for the project I'm working on. The software can handle it... it creates a P2P connection with another client (outside the cluster) and when the pod needs to restart, would be nice to maintain the same IP:port for the P2P network it's connecting to.
This tool has been super useful! Feature request: It'd be nice if there was a way to generate the same, unique port for each pod every time. I'm using a
StatefulSet
with 5 replicas and would like to guarantee thatpod-0
throughpod-5
always get the same unique port. I don't really care what the external ports are, as long as they stay the same.The text was updated successfully, but these errors were encountered: