K
Q

What's the difference between Kubernetes-native and non-native applications?

4/4/2018

From the Kubernetes docs:

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.

What is the exact difference between Kubernetes-native and non-native applications?

-- Emre Kenci
kubernetes

Similar Questions

Get an external IP for a Kubernetes LoadBalancer on Openstack
Where is the best practice place to put kubernetes monitoring?
Kubernetes Daemonset's mounted volumes show no logs/not collecting data
Read-only file system: MongoDB Cluster on Kubernetes using Helm charts

2 Answers

4/4/2018

I found the same section and interpret it as :

  • native are apps that are packed up and run inside k8s as some ‚kind‘. All dockerized apps should be in that category.
  • 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.
-- thst
Source: StackOverflow
9/17/2018

From my interpretation, non-native applications are Services-without-selectors, for which end-point are not created,(such as application running in different namespace, running outside kubernetes, development databases etc.)

-- PURVESH PATEL
Source: StackOverflow