[solved!] AWS load balancer not being created. help?

Archive Rancher 1.x
3

We figured out that we needed to do two things:

  1. Change the default Kubernetes template configuration to use the “aws” cloud provider.

  2. Grant various policy permissions to every rancher host we add to the cluster, which we do with a Role/InstanceProfile. The particular policy needed is:

    {“Version”:“2012-10-17”,“Statement”:[{“Action”:“elasticloadbalancing:",“Resource”:"”,“Effect”:“Allow”}]}

I posted details in How To: Deploy Rancher/Kubernetes in Amazon VPC private subnet