From fbe25cf9296230a720002aa326f58ec64f4f5d46 Mon Sep 17 00:00:00 2001 From: Kelsey Hightower Date: Sun, 11 Sep 2016 03:02:27 -0700 Subject: [PATCH] add support for aws --- docs/02-certificate-authority.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/02-certificate-authority.md b/docs/02-certificate-authority.md index 1d3d785..5395c93 100644 --- a/docs/02-certificate-authority.md +++ b/docs/02-certificate-authority.md @@ -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. -### Set the Kubernetes Public IP Address +### Set the Kubernetes Public Address #### GCE ``` -KUBERNETES_PUBLIC_IP_ADDRESS=$(gcloud compute addresses describe kubernetes \ +KUBERNETES_PUBLIC_ADDRESS=$(gcloud compute addresses describe kubernetes \ --format 'value(address)') ``` #### AWS ``` -KUBERNETES_PUBLIC_IP_ADDRESS=$(aws elb describe-load-balancers \ +KUBERNETES_PUBLIC_ADDRESS=$(aws elb describe-load-balancers \ --load-balancer-name kubernetes | \ jq -r '.LoadBalancerDescriptions[].DNSName') ``` @@ -159,7 +159,7 @@ cat > kubernetes-csr.json <