Action 545 includes routing the packet to the selected second service pod upon egress from the first service pod.
If the flow table lacks an entry corresponding to the header data, take action 555 accessing an available pods list in a consistent hash (lookup) table (CHT) of service pods performing the second service.
At action 565, select one of the available pods using a six-tuple hash as a key to the CHT table to select the second service pod, and update the flow table to specify the second service pod as providing the second service for packets sharing the header data.
Other implementations may perform the actions in different orders and/or with different, fewer or additional actions than those illustrated in