Step 3. Test the deployment - Modular and Scalable Amazon EKS Architecture

Step 3. Test the deployment

  1. Connect to the bastion host by using SSH with the key pair that you specified during deployment and the IP address in that is displayed on the Outputs tab of the CloudFormation stack.

  2. The bastion host already has kubectl installed and configured to be able to connect to the cluster. To test the CLI’s ability to connect to the cluster, run the following command.

    $ kubectl version

    Confirm that the output includes the Server Version, which indicates a successful connection the Kubernetes control plane:

      Client Version: version.Info{Major:"1",
      Minor:"11", GitVersion:"<version number>",
      GitCommit:"<commit ID>",
      GitTreeState:"clean",
      BuildDate:"2018-12-06T01:33:57Z",
      GoVersion:"go1.10.3", Compiler:"gc",
      Platform:"linux/amd64"}
      Server Version: version.Info{Major:"1",
      Minor:"11+", GitVersion:"<version number>",
      GitCommit:"<commit ID>",
      GitTreeState:"clean",
      BuildDate:"2018-12-06T23:13:14Z",
      GoVersion:"go1.10.3", Compiler:"gc",
      Platform:"linux/amd64"}
      
  3. Now check that the nodes have successfully connected to the cluster by running the get nodes command.

    $ kubectl get nodes NAME STATUS ROLES AGE VERSION ip-10-0-25-239.us-west-2.compute.internal Ready <none> 10m <version number> ip-10-0-27-244.us-west-2.compute.internal Ready <none> 10m <version number> ip-10-0-35-29.us-west-2.compute.internal Ready <none> 10m <version number>