Skip to content

Commit 3f10a19

Browse files
lab12-smoke-test.md
Grammar check
1 parent 24e475a commit 3f10a19

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

docs/labs/kubernetes-the-hard-way/lab12-smoke-test.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
author: Wale Soyinka
3-
contributors: Steven Spencer
3+
contributors: Steven Spencer, Ganna Zhyrnova
44
tags:
55
- kubernetes
66
- k8s
@@ -13,13 +13,13 @@ tags:
1313

1414
# Lab 12: Smoke Test
1515

16-
> This is a fork of the original ["Kubernetes the hard way"](https://github.com/kelseyhightower/kubernetes-the-hard-way) originally written by Kelsey Hightower (GitHub: kelseyhightower). Unlike the original that bases itself on Debian like distributions for the ARM64 architecture, this fork targets Enterprise Linux distributions such as Rocky Linux running on x86_64 architecture.
16+
> This is a fork of the original ["Kubernetes the hard way"](https://github.com/kelseyhightower/kubernetes-the-hard-way) originally written by Kelsey Hightower (GitHub: kelseyhightower). Unlike the original, which bases itself on Debian-like distributions for the ARM64 architecture, this fork targets Enterprise Linux distributions such as Rocky Linux, which runs on x86_64 architecture.
1717
18-
In this lab you will complete a series of tasks to ensure your Kubernetes cluster is functioning correctly.
18+
In this lab, you will complete tasks to ensure your Kubernetes cluster functions correctly.
1919

2020
## Data Encryption
2121

22-
In this section you will verify the ability to [encrypt secret data at rest](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#verifying-that-data-is-encrypted).
22+
In this section, you will verify the ability to [encrypt secret data at rest](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#verifying-that-data-is-encrypted).
2323

2424
Create a generic secret:
2525

@@ -65,7 +65,7 @@ You need to prefix the `etcd` key with `k8s:enc:aescbc:v1:key1`, which indicates
6565

6666
## Deployments
6767

68-
In this section you will verify the ability to create and manage [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/).
68+
In this section, you will verify the ability to create and manage [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/).
6969

7070
Create a deployment for the [nginx](https://nginx.org/en/) web server:
7171

@@ -87,7 +87,7 @@ nginx-54c98b4f84-dfwl9 1/1 Running 0 71s
8787

8888
### Port Forwarding
8989

90-
In this section you will verify the ability to access applications remotely using [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/).
90+
In this section, you will verify the ability to access applications remotely using [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/).
9191

9292
Retrieve the full name of the `nginx` pod:
9393

@@ -107,7 +107,7 @@ Forwarding from 127.0.0.1:8080 -> 80
107107
Forwarding from [::1]:8080 -> 80
108108
```
109109

110-
In a new terminal make an HTTP request with the forwarding address:
110+
In a new terminal, make an HTTP request with the forwarding address:
111111

112112
```bash
113113
curl --head http://127.0.0.1:8080
@@ -136,7 +136,7 @@ Handling connection for 8080
136136

137137
### Logs
138138

139-
In this section you will verify the ability to [retrieve container logs](https://kubernetes.io/docs/concepts/cluster-administration/logging/).
139+
In this section, you will verify the ability to [retrieve container logs](https://kubernetes.io/docs/concepts/cluster-administration/logging/).
140140

141141
Print the `nginx` pod logs:
142142

@@ -151,7 +151,7 @@ kubectl logs $POD_NAME
151151

152152
### Exec
153153

154-
In this section you will verify the ability to [execute commands in a container](https://kubernetes.io/docs/tasks/debug-application-cluster/get-shell-running-container/#running-individual-commands-in-a-container).
154+
In this section, you will verify the ability to [execute commands in a container](https://kubernetes.io/docs/tasks/debug-application-cluster/get-shell-running-container/#running-individual-commands-in-a-container).
155155

156156
Print the `nginx` version by executing the `nginx -v` command in the `nginx` container:
157157

@@ -165,7 +165,7 @@ nginx version: nginx/1.27.4
165165

166166
## Services
167167

168-
In this section you will verify the ability to expose applications with a [Service](https://kubernetes.io/docs/concepts/services-networking/service/).
168+
In this section, you will verify the ability to expose applications with a [Service](https://kubernetes.io/docs/concepts/services-networking/service/).
169169

170170
Expose the `nginx` deployment using a [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport) service:
171171

@@ -174,7 +174,7 @@ kubectl expose deployment nginx \
174174
--port 80 --type NodePort
175175
```
176176

177-
> You cannot use the LoadBalancer service type because your cluster is not configured with [cloud provider integration](https://kubernetes.io/docs/getting-started-guides/scratch/#cloud-provider). Setting up cloud provider integration is out of scope for this tutorial.
177+
> You cannot use the LoadBalancer service type because your cluster is not configured with [cloud provider integration](https://kubernetes.io/docs/getting-started-guides/scratch/#cloud-provider). This tutorial does not cover setting up cloud provider integration.
178178
179179
Retrieve the node port assigned to the `nginx` service:
180180

0 commit comments

Comments
 (0)