Open senyan opened 6 years ago
Any attention on this, please? @philips (you are the first guy come up in this org when I hit '@' )
All things needed is make the pod name consistent, say a cluster of 3 nodes, always make the etcd-pod name to be (etcd-1, etcd-2, etcd-3) in any events (crash, failures, backups), rather than infinitely add new pod with random name (current behavior). The Kubernetes scheduler will schedule the pod to the right node.
@senyan we are working on adding new features like this. We would really like your help are you interested in getting involved?
@hexfusion For this feature I think I can contribute. I will make a PR.
@senyan thanks that would be amazing!
Any news on this one?
Any progress? IMO, make pod name stable like statefulset instead of random suffix, will resolve a lot of things, such as pv and dns address.
To be honest, I just started using a normal StatefulSet. Requires more expert knowledge, sure, but you get more fine grained control, and is less "magic" (in a good way).
Kubernetes 1.10+ has a new cool feature called local volumes. Is there any plan to support the pod to use it? Something like the volume-template in the statefulset.