chg: Hostname In Documetation

Changed the hostname to fit thouse used with the virtual machines.
pull/882/head
Khalifah Shabazz 2025-06-01 14:19:57 -04:00
parent f466bc3e28
commit df00134866
2 changed files with 46 additions and 15 deletions

View File

@ -1,19 +1,30 @@
# Prerequisites
In this lab you will review the machine requirements necessary to follow this tutorial.
In this lab you will review the machine requirements necessary to follow this
tutorial.
## Virtual or Physical Machines
This tutorial requires four (4) virtual or physical ARM64 or AMD64 machines running Debian 12 (bookworm). The following table lists the four machines and their CPU, memory, and storage requirements.
This tutorial requires four (4) virtual or physical ARM64 or AMD64 machines
running Debian 12 (bookworm). The following table lists the four machines and
their CPU, memory, and storage requirements.
| Name | Description | CPU | RAM | Storage |
|---------|------------------------|-----|-------|---------|
| jumpbox | Administration host | 1 | 512MB | 10GB |
| server | Kubernetes server | 1 | 2GB | 20GB |
| node-0 | Kubernetes worker node | 1 | 2GB | 20GB |
| node-1 | Kubernetes worker node | 1 | 2GB | 20GB |
| Name | Description | CPU | RAM | Storage |
|--------------|------------------------|-----|-------|---------|
| jumpbox | Administration host | 1 | 512MB | 10GB |
| controlplane | Kubernetes server | 1 | 2GB | 20GB |
| node01 | Kubernetes worker node | 1 | 2GB | 20GB |
| node02 | Kubernetes worker node | 1 | 2GB | 20GB |
How you provision the machines is up to you, the only requirement is that each machine meet the above system requirements including the machine specs and OS version. Once you have all four machines provisioned, verify the OS requirements by viewing the `/etc/os-release` file:
How you provision the machines is up to you, the only requirement is that each
machine meet the above system requirements including the machine specs and OS
version.
We provide [virtual machines] that act as a blank environment. It can be spun
up locally with Vagrant and either VirtualBox or HyperV.
Once you have all four machines provisioned, verify the OS requirements by
viewing the `/etc/os-release` file:
```bash
cat /etc/os-release
@ -22,12 +33,21 @@ cat /etc/os-release
You should see something similar to the following output:
```text
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
```
Next: [setting-up-the-jumpbox](02-jumpbox.md)
---
[virtual machines]: /virtual-machines/README.md

View File

@ -1,5 +1,16 @@
# Smoke Test
## Add kubectl Alias
So you can just type `k` in place of `kubectl` for running Kubernetes commands.
Run `k` on the command like to make sure it is not already in use. You should
get an error that it is an unknown command. Then run:
```shell
echo "alias k=kubectl" | tee -a ~/.bashrc && source ~/.bashrc
```
In this lab you will complete a series of tasks to ensure your Kubernetes cluster is functioning correctly.
## Data Encryption