If moving the conversation to slack, it would be great to post back to the list with a summary!
On Mon, Jan 29, 2018 at 1:38 PM, Vinod Kone <[email protected]> wrote: > Hi David, > > It's probably worth having a synchronous discussion around your proposed > approach in our slack. I would like to understand if TASK_GROUP is the > right primitive for your use case. > > On Mon, Jan 29, 2018 at 1:32 PM, David Morrison <[email protected]> wrote: > >> >> >> On Thu, Jan 25, 2018 at 5:49 PM, Gilbert Song <[email protected]> >> wrote: >> >>> >>>> - >>>> >>>> Is it possible to allocate a separate IP address per container in a >>>> pod? >>>> >>>> Right now nested containers share the network from their parent >>> container (pod). Do we have a specific use case that we need containers >>> inside of a taskgroup have different IP addresses? >>> >> >> For our use case, we need to be able to launch a relatively large number >> of containers inside a taskgroup that all listen on the same port (and the >> port is not easily-changeable). So we need to be able to assign different >> IPs to the containers so they don't conflict. >> >> Cheers, >> David >> > >
