github.com/kubernetes-incubator/kube-aws@v0.16.4/docs/getting-started/step-3-launch.md (about)

     1  # Launch your Kubernetes cluster on AWS
     2  
     3  This is the [third step of running Kubernetes on AWS](README.md). We're ready to launch the Kubernetes cluster.
     4  
     5  ## Create the instances defined in the CloudFormation template
     6  
     7  Now for the exciting part, creating your cluster:
     8  
     9  ```sh
    10  $ kube-aws apply
    11  ```
    12  
    13  **NOTE**: It can take some time after `kube-aws apply` completes before the cluster is available. When the cluster is first being launched, it must download all container images for the cluster components (Kubernetes, dns, metrics, etc). Depending on the speed of your connection, it can take a few minutes before the Kubernetes api-server is available.
    14  
    15  ## Configure DNS
    16  
    17  If you configured Route 53 settings in your configuration above via `createRecordSet`, a host record has already been created for you.
    18  
    19  Otherwise, navigate to the DNS registrar hosting the zone for the provided external DNS name. Ensure a single A record exists, routing the value of `externalDNSName` defined in `cluster.yaml` to the externally-accessible IP of the master node instance.
    20  
    21  You can invoke `kube-aws status` to get the cluster API endpoint after cluster creation, if necessary. This command can take a while.
    22  
    23  ## Access the cluster
    24  
    25  A kubectl config file will be written to a `kubeconfig` file, which can be used to interact with your Kubernetes cluster like so:
    26  
    27  ```sh
    28  $ kubectl --kubeconfig=kubeconfig get nodes
    29  ```
    30  
    31  If the container images are still downloading and/or the API server isn't accessible yet, the kubectl command above may show output similar to:
    32  
    33  ```
    34  The connection to the server <externalDNSName>:443 was refused - did you specify the right host or port?
    35  ```
    36  
    37  Wait a few more minutes for everything to complete.
    38  
    39  Once the API server is running, you should see:
    40  
    41  ```sh
    42  $ kubectl --kubeconfig=kubeconfig get nodes
    43  NAME                                       STATUS                     AGE
    44  ip-10-0-0-xxx.us-west-1.compute.internal   Ready                      5m
    45  ip-10-0-0-xxx.us-west-1.compute.internal   Ready                      5m
    46  ip-10-0-0-xx.us-west-1.compute.internal    Ready,SchedulingDisabled   5m
    47  ```
    48  
    49  <div class="co-m-docs-next-step">
    50    <p><strong>You're all done!</strong> The cluster is ready to use.</p>
    51    <p>For full lifecycle information, read on below.</p>
    52  </div>
    53  
    54  ## Export the CloudFormation stack
    55  
    56  If you want to share, audit or back up your stack, use the export flag:
    57  
    58  ```sh
    59  $ kube-aws apply --export
    60  ```
    61  
    62  Once you have successfully launched your cluster, you are ready to [update your cluster][getting-started-step-4].
    63  
    64  [getting-started-step-1]: step-1-configure.md
    65  [getting-started-step-2]: step-2-render.md
    66  [getting-started-step-3]: step-3-launch.md
    67  [getting-started-step-4]: step-4-update.md
    68  [getting-started-step-5]: step-5-add-node-pool.md
    69  [getting-started-step-6]: step-6-configure-add-ons.md
    70  [getting-started-step-7]: step-7-destroy.md