Table of Contents

1. Challenge

   Create a Cluster, With a Private Topology, and Secure the Bastion Host

   1. The script, k8s-create-ac.sh has been provided for this lab. Review the script with the cat command.
   2. Create the cluster config files by executing the lab-provided script. Review the cluster configuration.
   3. Initialize the cluster.

   Note: This is not the bastion host created as a jump box. This is a new bastion host, created by kops that is inside the vpc, with the master and worker nodes.

2. Challenge

   Using the RSA Key, SSH to the Bastion Host, and Attempt to Access the Master Node

   1. Use the ssh command provided during the cluster initialization to establish a terminal session on the secure bastion host.
   2. In the AWS Console, take note of the IP addresses provided to the secure bastion host.
   3. From the secure bastion host, attempt to access the Kubernetes Master with ssh.
3. Challenge

   Using an SSH Agent, Connect to the Secure Bastion Host, and Attempt to Access the Master Node

   1. Using eval, check if an SSH agent is already running.
   2. Add the private RSA key as an identity.
   3. Connect to the secure bastion host, and attempt to connect to the master node using the private IP address.
   4. Verify that you have successfully connected to the master node.
4. Challenge

   From the Master Node, Interrogate the Configuration, and Run the kube-bench Utility

   1. Review the kube-apiserver.manifest file in the /etc/kubernetes/manifests directory.
   2. Review the kube config file.
   3. Install version 0.3.1 of the kube-bench utility.
   4. Execute a kube-bench run against the master node, and review the results.
5. Challenge

   Using an SSH Session, From the Secure Bastion Host, Execute kubectl Remotely

   1. Using an ssh session from the bastion host, run the kubectl get nodes command on the master node.
   2. From the bastion host, list all running pods, in all namespaces.
   3. From the bastion host, create a pod using the example pod.yaml file, in the course GitHub repository.
   4. Verify that the pod was created successfully.
6. Challenge

   From the AWS Console, Stop the Secure Bastion Host

   1. In the AWS Console, navigate to the EC2 Dashboard, and view the running instances.
   2. Select the secure bastion host from the list, and use the Instance State menu to stop the instance.