I understand nomad, and what you're saying is not how anyone runs it. Directly from their documentation: "Nomad schedules workloads of various types across a c

I understand nomad, and what you're saying is not how anyone runs it. Directly from their documentation: "Nomad schedules workloads of various types across a cluster of generic hosts. Because of this, placement is not known in advance and you will need to use service discovery to connect tasks to other services deployed across your cluster. Nomad integrates with Consul to provide service discovery and monitoring." So one of the very basic features of an orchestrator, which is service discovery, requires consul. Sure, I can use it without consul to just start jobs that don't communicate, but obviously that's that the normal use case of it, and you can see that by looking at their issues list.