So far, all the details we have explored have been related to a single container running within Kubernetes. The significant benefits of leveraging Kubernetes start to come into play when leveraging many containers running together. Being able to group together a set of Pods that all do the same thing, so that we can scale them and access them, is what the Kubernetes resource Service is all about.
A Service is the Kubernetes resource used to provide an abstraction through to your Pod (or Pods) that is agnostic of the specific instances that are running. Providing a layer between what one container (or set of containers) provides, such as a frontend web application, and another layer, such as a database, allows Kubernetes to scale them independently, update them, handle scaling issues, and more. A service also can contain a policy by which data should be transferred, so you might consider it a software load balancer within Kubernetes.
A Service is also the key...
