From 28bd5c62f85a4645ce79808253ae3eea5181fade Mon Sep 17 00:00:00 2001 From: Mumshad Date: Wed, 20 Mar 2019 14:52:05 +0800 Subject: [PATCH] minor updates --- README.md | 4 +- docs/02-client-tools.md | 37 ----------- ...e-resources.md => 02-compute-resources.md} | 0 docs/03-client-tools.md | 62 +++++++++++++++++++ docs/04-certificate-authority.md | 11 +--- 5 files changed, 65 insertions(+), 49 deletions(-) delete mode 100644 docs/02-client-tools.md rename docs/{03-compute-resources.md => 02-compute-resources.md} (100%) create mode 100644 docs/03-client-tools.md diff --git a/README.md b/README.md index 3af49ab..df13b2d 100644 --- a/README.md +++ b/README.md @@ -31,8 +31,8 @@ Kubernetes The Hard Way guides you through bootstrapping a highly available Kube ## Labs * [Prerequisites](docs/01-prerequisites.md) -* [Installing the Client Tools](docs/02-client-tools.md) -* [Provisioning Compute Resources](docs/03-compute-resources.md) +* [Provisioning Compute Resources](docs/02-compute-resources.md) +* [Installing the Client Tools](docs/03-client-tools.md) * [Provisioning the CA and Generating TLS Certificates](docs/04-certificate-authority.md) * [Generating Kubernetes Configuration Files for Authentication](docs/05-kubernetes-configuration-files.md) * [Generating the Data Encryption Config and Key](docs/06-data-encryption-keys.md) diff --git a/docs/02-client-tools.md b/docs/02-client-tools.md deleted file mode 100644 index 018abf0..0000000 --- a/docs/02-client-tools.md +++ /dev/null @@ -1,37 +0,0 @@ -# Installing the Client Tools - -In this lab you will install the command line utilities required to complete this tutorial: [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl). - -## Install kubectl - -The `kubectl` command line utility is used to interact with the Kubernetes API Server. Download and install `kubectl` from the official release binaries: - -### Linux - -``` -wget https://storage.googleapis.com/kubernetes-release/release/v1.13.0/bin/linux/amd64/kubectl -``` - -``` -chmod +x kubectl -``` - -``` -sudo mv kubectl /usr/local/bin/ -``` - -### Verification - -Verify `kubectl` version 1.13.0 or higher is installed: - -``` -kubectl version --client -``` - -> output - -``` -Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T21:04:45Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"} -``` - -Next: [Provisioning Compute Resources](03-compute-resources.md) diff --git a/docs/03-compute-resources.md b/docs/02-compute-resources.md similarity index 100% rename from docs/03-compute-resources.md rename to docs/02-compute-resources.md diff --git a/docs/03-client-tools.md b/docs/03-client-tools.md new file mode 100644 index 0000000..d2ba54a --- /dev/null +++ b/docs/03-client-tools.md @@ -0,0 +1,62 @@ +# Installing the Client Tools + +First identify a system from where you will perform administrative tasks, such as creating certificates, kubeconfig files and distributing them to the different VMs. + +If you are on a Linux laptop, then your laptop could be this system. In my case I chose the master-1 node to perform administrative tasks. Whichever system you chose make sure that system is able to access all the provisioned VMs through SSH to copy files over. + +## Access all VMs + +Generate Key Pair on master-1 node +`$ssh-keygen` + +Leave all settings to default. + +View the generated public key ID at: + +``` +$cat .ssh/id_rsa.pub +ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQD......8+08b vagrant@master-1 +``` + +Move public key of master to all other VMs + +``` +$cat >> ~/.ssh/authorized_keys < output + +``` +Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T21:04:45Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"} +``` + +Next: [Provisioning Compute Resources](03-compute-resources.md) diff --git a/docs/04-certificate-authority.md b/docs/04-certificate-authority.md index a4466cd..6bbb495 100644 --- a/docs/04-certificate-authority.md +++ b/docs/04-certificate-authority.md @@ -6,17 +6,8 @@ In this lab you will provision a [PKI Infrastructure](https://en.wikipedia.org/w You can do these on any machine with `openssl` on it. But you should be able to copy the generated files to the provisioned VMs. Or just do these from one of the master nodes. -In my case I do it on the master-1 node, so I create an SSH key pair from the master-1 node and place them in the authorized_keys on the other nodes. +In our case we do it on the master-1 node, as we have set it up to be the administrative client. -Generate Key Pair on master-1 node -`ssh-keygen` - -Move public key to other nodes - -```cat >> ~/.ssh/authorized_keys <