<p>Service abstract Pod IP address from consumers, load balances between pods, relies on labels to associate a service with a Pod, holds virtual IP provided by Node's kube-proxy, non-ephemeral</p>
<p>Given below services:</p>
<pre><code>$ kubectl -n mynamespace get services | more
NAME         TYPE          CLUSTER-IP        EXTERNAL-IP   PORT(S)                                          AGE
my-app1     NodePort   192.168.112.249   &lt;none&gt;            80:32082/TCP,2121:30581/TCP   50d
my-app2    NodePort   192.168.113.154   &lt;none&gt;             80:30704/TCP,2121:30822/TCP   50d
my-app3    NodePort   192.168.114.232   &lt;none&gt;            80:32541/TCP,2121:32733/TCP   5d2h
my-app4    NodePort   192.168.115.182    &lt;none&gt;             80:30231/TCP,2121:30992/TCP   5d2h
</code></pre>
<hr />
<p>Is &quot;service&quot; type kubernetes object launched as a separate Pod container in data plane?</p>

overexchange
<blockquote>
<p>Is &quot;service&quot; type kubernetes object launched as a separate Pod container in data plane?</p>
</blockquote>
<p>Nope, a <code>Service</code> is an <strong><em>abstract</em></strong> resource in Kubernetes.</p>
<p>From the <a href="https://kubernetes.io/docs/concepts/services-networking/service/" rel="nofollow noreferrer">Service</a> documentation:</p>
<blockquote>
<p>An abstract way to expose an application running on a set of Pods as a network service.
With Kubernetes you don't need to modify your application to use an unfamiliar service discovery mechanism. Kubernetes gives Pods their own IP addresses and a single DNS name for a set of Pods, and can load-balance across them.</p>
</blockquote>
