Setting up an HA Kubernetes cluster with private networking in AWS

I wrote a similar article a while ago; except using Rancher - Which adds extra features for infrastructure management. <a href="https:&#x2F;&#x2F;blog.baasil.io&#x2F;how-to-install-kubernetes-on-aws-d9fbbc04e816#.cnqfv841r" rel="nofollow">https:&#x2F;&#x2F;blog.baasil.io&#x2F;how-to-install-kubernetes-on-aws-d9fb...</a>

Good lord this is so much easier than it was 6 months ago. Really glad to see the barrier of entry going down to get these clusters built. Kubernetes has been paramount to our engineering growth at FarmLogs.

kops is pretty great for managing the lifecycle of a k8s cluster. It even supports outputting Terraform code, if that is your Infrastructure-as-Code tool of choice.

ECS tasks now support IAM roles; how does this work for K8s equivalent? Do you need to use IAM user credentials for app credentials?

kops is nice... but too tied to AWS.<p>I&#x27;m really liking the direction that kargo is taking. It leverages a well known toolset - ansible - to build out its functionality.<p>kargo is compatible with everything from bare metal to AWS... with the caveat that when using it in AWS, you have to use a different provisioning tool like Terraform.<p>This is a feature.. not a bug.

This is a nice write up, but we honestly needed to stand up kubernetes on-premise and in public&#x2F;private clouds. This is why we&#x27;ve been using this: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=B7nMFVaOOi8" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=B7nMFVaOOi8</a>