Getting started with microservices and kubernetes

Two pieces of feedback.<p>First, tutorials like this should include getting this running using TLS by default. Ideally there shouldn&#x27;t be any reference to plain http at all.<p>Second, the DSL for Kube and Ambassador seem ridiculously complex for this. Maybe some explanation for what &quot;imagePullPolicy: IfNotPresent&quot; means? This kind of configuration harkens back to the myriad of Jboss XML files, just in a different format. For me personally, I get all the reasons why you&#x27;d want to use k8s, but for a &quot;getting started&quot; user, seeing this kind of required config -- rather than sensible defaults hidden away -- would get very discouraging. (&quot;Why should I learn this DSL instead of just making sure I had a correct puppet setup?&quot;)

I think this is an excellent introduction to the tech side.<p>I do sometimes think that &quot;Getting started&quot; articles should sometimes be prefaced with a &quot;here&#x27;s who this isn&#x27;t for&quot; - particularly with architectures designed for scale not simplicity. I tend to think if you&#x27;re in a situation that demands microservices, you should already know the tech stuff :-) The hard bit about getting started is really reconfiguring the team.

So tell me why I should prefer this over Consul for service discovery, health checking, etc. and Nomad for running jobs? With Nomad, I can choose raw executables, shell scriots, jar files, docker containers, etc. I can choose batch jobs or long running services and the executables for each are less than 60Mb and they can serve as servers and clients.