Well, a super common use case would be where you were canary testing two deployments. You might have "foo-1.1" and "foo-1.2-canary" both of which had the label "foo". The system would automatically send a small amount of traffic to the canary ( (# of foo-1.2-canary pods / (# foo-1.1 pods + # of foo-1.2-canary pods) ) % to be exact ), and the service would span two templates.
On Wed, Sep 7, 2016 at 12:42 AM, Mayank <[email protected]> wrote: > Hi All > I wanted to know about peoples use cases where they had to create a > kubernetes service whose selector spans across multiple pod templates. I am > trying to see if this is a good recommended way for doing things, or > generally this is a bad design which smells and probably the pods template > is to blame. I dont have any use case myself, just thinking out loud on if > there are real use cases community found where the only way around was > having a service span across different pod templates since they could not > have those pods containers all as part of one pod. > > Thoughts ? > -Mayank > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
