Hi All
We are evaluating a use case which requires each pod to be exposed as a
service or on some well known nodeport. I understand that there is some
work going on for 1.3 in the name of PetSet. I wanted to know if it
fulfills everything we need or what the community/designers are thinking
about those use cases and its current status in master branch:-
1. My application is composed of n pods
2. We want each pod to be exposed on some well known nodeport or expose
as a service that can be accessible from outside k8s. So traffic can be
directed to the pod directly and the specific pod is always accessible at
predetermined well known nodeport or ip.
3. If those pods die and come up back, they should still be visible on
the same nodeport or service ip.
4. If i add more pods to my application, they should dynamically get
assigned a well known service ip from predefined set of ip pool
5. The application with n pods can still be updated using rolling update
as a unit of deployment.
Please let me know if this makes sense and whether the current PetSet
supports this or a modified form of it can be supported. I am open to
hearing what other use cases the community has and how we are solving it
Mayank
--
You received this message because you are subscribed to the Google Groups
"Containers at Google" 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/google-containers.
For more options, visit https://groups.google.com/d/optout.
