The short answer is that you are ascribing identity to pods that don't really have any. They are literally called "replicas". If you need identity, you really sort of want StatefulSet. If that doesn't work, it would be good to understand more concretely what you're trying to achieve.
On Thu, Mar 1, 2018 at 1:22 AM, <james.mas...@jmips.co.uk> wrote: > Hi list, > > I'm following this guide: > https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pods-hostname-and-subdomain-fields > > I wish to have each pod in a deployment have a unique hostname, which allows > another pod to contact each of the autoscaled pods by hostname. > > However, although the guide makes sense for individual pods, it does not work > for deployments, as due to the lack of parameterisation each pod hostname set > would be the same. > > Can anyone think of a way around this? > > I've considered StatefulSet, but the lifecycle of the pods doesn't really fit > this model. > > thanks > > James M > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
