add support for aws

pull/48/merge
Kelsey Hightower 2016-09-11 03:02:27 -07:00
parent 02f4bef7b3
commit fbe25cf929
1 changed files with 4 additions and 4 deletions

View File

@ -120,19 +120,19 @@ openssl x509 -in ca.pem -text -noout
In this section we will generate a TLS certificate that will be valid for all Kubernetes components. This is being done for ease of use. In production you should strongly consider generating individual TLS certificates for each component. In this section we will generate a TLS certificate that will be valid for all Kubernetes components. This is being done for ease of use. In production you should strongly consider generating individual TLS certificates for each component.
### Set the Kubernetes Public IP Address ### Set the Kubernetes Public Address
#### GCE #### GCE
``` ```
KUBERNETES_PUBLIC_IP_ADDRESS=$(gcloud compute addresses describe kubernetes \ KUBERNETES_PUBLIC_ADDRESS=$(gcloud compute addresses describe kubernetes \
--format 'value(address)') --format 'value(address)')
``` ```
#### AWS #### AWS
``` ```
KUBERNETES_PUBLIC_IP_ADDRESS=$(aws elb describe-load-balancers \ KUBERNETES_PUBLIC_ADDRESS=$(aws elb describe-load-balancers \
--load-balancer-name kubernetes | \ --load-balancer-name kubernetes | \
jq -r '.LoadBalancerDescriptions[].DNSName') jq -r '.LoadBalancerDescriptions[].DNSName')
``` ```
@ -159,7 +159,7 @@ cat > kubernetes-csr.json <<EOF
"10.240.0.30", "10.240.0.30",
"10.240.0.31", "10.240.0.31",
"10.240.0.32", "10.240.0.32",
"${KUBERNETES_PUBLIC_IP_ADDRESS}", "${KUBERNETES_PUBLIC_ADDRESS}",
"127.0.0.1" "127.0.0.1"
], ],
"key": { "key": {