<p>From the <a href="https://kubernetes.io/docs/concepts/services-networking/service/" rel="noreferrer">Kubernetes docs</a>:</p>

<blockquote>
  <p>For Kubernetes-native applications, Kubernetes offers a simple Endpoints API that is updated whenever the set of Pods in a Service changes. For non-native applications, Kubernetes offers a virtual-IP-based bridge to Services which redirects to the backend Pods.</p>
</blockquote>

<p>What is the exact difference between Kubernetes-native and non-native applications?</p>

<p>I found the same section and interpret it as :</p>

<ul>
<li>native are apps that are packed up and run inside k8s as some ‚kind‘. All dockerized apps should be in that category.</li>
<li>non native is connected with the k8s cluster infrastructure but not deployed within. A legacy app, an Oracle cluster or your backup robot may fall in this category.</li>
</ul>
