mirrors/kubernetes-the-hard-way
1
0
Fork 0
mirror of https://github.com/kelseyhightower/kubernetes-the-hard-way.git synced 2025-12-15 17:28:58 +03:00
Code Issues Projects Releases Wiki Activity

chg: Hostnames In Documentation Continued

Browse Source 
Updated more references to old hostnames in the documentation to reflect
the new naming convention.
This commit is contained in:
Khalifah Shabazz
2025-06-01 23:37:55 -04:00
parent 1889697098
commit 398f5a73c0
13 changed files with 160 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/08-bootstrapping-kubernetes-controllers.md
View File

@@ -1,10 +1,10 @@
# Bootstrapping the Kubernetes Control Plane
In this lab you will bootstrap the Kubernetes control plane. The following components will be installed on the `server` machine: Kubernetes API Server, Scheduler, and Controller Manager.
In this lab you will bootstrap the Kubernetes control plane. The following components will be installed on the `controlplane` machine: Kubernetes API Server, Scheduler, and Controller Manager.
## Prerequisites
Connect to the `jumpbox` and copy Kubernetes binaries and systemd unit files to the `server` machine:
Connect to the `jumpbox` and copy Kubernetes binaries and systemd unit files to the `controlplane` machine:
```bash
scp \
@@ -17,13 +17,13 @@ scp \
units/kube-scheduler.service \
configs/kube-scheduler.yaml \
configs/kube-apiserver-to-kubelet.yaml \
root@server:~/
root@controlplane:~/
```
The commands in this lab must be run on the `server` machine. Login to the `server` machine using the `ssh` command. Example:
The commands in this lab must be run on the `controlplane` machine. Login to the `controlplane` machine using the `ssh` command. Example:
```bash
ssh root@server
ssh root@controlplane
```
## Provision the Kubernetes Control Plane
@@ -54,7 +54,7 @@ Install the Kubernetes binaries:
mkdir -p /var/lib/kubernetes/
mv ca.crt ca.key \
kube-api-server.key kube-api-server.crt \
kube-apiserver.key kube-apiserver.crt \
service-accounts.key service-accounts.crt \
encryption-config.yaml \
/var/lib/kubernetes/
@@ -155,10 +155,10 @@ In this section you will configure RBAC permissions to allow the Kubernetes API
> This tutorial sets the Kubelet `--authorization-mode` flag to `Webhook`. Webhook mode uses the [SubjectAccessReview](https://kubernetes.io/docs/reference/access-authn-authz/authorization/#checking-api-access) API to determine authorization.
The commands in this section will affect the entire cluster and only need to be run on the `server` machine.
The commands in this section will affect the entire cluster and only need to be run on the `controlplane` machine.
```bash
ssh root@server
ssh root@controlplane
```
Create the `system:kube-apiserver-to-kubelet` [ClusterRole](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-and-clusterrole) with permissions to access the Kubelet API and perform most common tasks associated with managing pods:
@@ -172,7 +172,7 @@ kubectl apply -f kube-apiserver-to-kubelet.yaml \
At this point the Kubernetes control plane is up and running. Run the following commands from the `jumpbox` machine to verify it's working:
Make a HTTP request for the Kubernetes version info:
Make an HTTP request for the Kubernetes version info:
```bash
curl --cacert ca.crt \