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.
