Kubelet token distribution on AWS

[erictune]

Make #2387 work for AWS.

Suggested steps:

1. add the same lines to cluster/aws/templates/create-dynamic-salt-files.sh as Kubelet talks securely to apiserver #2387 added to cluster/gce/templates/create-dynamic-salt-files.sh
2. change {% if grains.cloud == "gce" %} to {% if grains.cloud in ["gce", "aws"] %} in cluster/saltbase/salt/kube-apiserver/default and cluster/saltbase/salt/kube-apiserver/init.sls
3. change if provider != "gce" to if provider != "gce" and provider != "aws" { in cmd/e2e/e2e.go
4. CLOUD_PROVIDER=aws hack/e2e-test.sh

[erictune]

I'd do it but I don't have an AWS account or any experience with AWS provider.

[erictune]

@kelseyhightower @justinsb
This should be pretty straightforward if you've run k8s on AWS before -- and I think you both have.

[bwahn]

@erictune I have a AWS acount. Can I test on AWS?

[bwahn]

@erictune After testing this issue, I will comment.

[erictune]

I realized that there are actually several separate AWS getting-started guides.
There is docs/getting-started-guides/aws.md which uses kube-up and there is docs/getting-started-guides/coreos.md which includes AWS.

[erictune]

At the same time as doing this work, also change the kube-proxy to set the flag:
--master=http://$APISERVER:7080.

[justinsb]

For work-coordination: I'm going to start my day today by doing this, at least for AWS/Ubuntu. I'm working in https://github.com/justinsb/kubernetes/tree/fix_aws

[erictune]

Awesome, thank

On Thu, Jan 29, 2015 at 6:41 AM, Justin Santa Barbara <
notifications@github.com> wrote:

For work-coordination: I'm going to start my day today by doing this, at
least for AWS/Ubuntu. I'm working in
https://github.com/justinsb/kubernetes/tree/fix_aws

—
Reply to this email directly or view it on GitHub
#2440 (comment)
.

[bwahn]

Great news~

[erictune]

looks fixed