Sure. What I mean by that is that if you use kubernetes, you will be using kubernetes service Discovery, endpoints, ingress, and volumes, where nomad is strictl

Sure. What I mean by that is that if you use kubernetes, you will be using kubernetes service Discovery, endpoints, ingress, and volumes, where nomad is strictly the scheduler. For example you can easily set up nomad with consul service discovery and then use the same consul instance for service discovery of services living outside nomad, such as legacy applications. It's hard to do something like that with Kube services because kubernetes comes with its own service discovery mechanism. For more comparison between the two schedulers coming from the point of view of someone who chose Nomad, look at this article https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896 https://medium.com/@copyconstruct/schedulers-kubernetes-and-... . I especially found his idea of incremental infrastructure improvement interesting, near the bottom if of the article.