Basically, it's not possible to do it with just a service. Service does not queue nor persist, so those guarantees that you just mention are not possible with just a service.
The idea of the service is to expose pods to other pods or the internet, so you can connect easily (and not worry about pods IP changing, etc.). Nothing else. So, queuing and persistency are out of scope. They are really a different thing services and rabbitmq :-( On Monday, December 11, 2017, <[email protected]> wrote: > Thanks. > > We are using RabbitMQ for queuing jobs and celery workers that are in > docker service as consumers of those jobs. > > -- > 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.
