From f1f108088851b88dd4e28ef955a6d2f26e798e1b Mon Sep 17 00:00:00 2001 From: Pick1a1username <20301273+Pick1a1username@users.noreply.github.com> Date: Sun, 17 Feb 2019 18:49:57 +0900 Subject: [PATCH] The chapter 'Generating the Data Encryption Config and Key' is updated. --- docs/06-data-encryption-keys.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/06-data-encryption-keys.md b/docs/06-data-encryption-keys.md index f44eed9..37f3d09 100644 --- a/docs/06-data-encryption-keys.md +++ b/docs/06-data-encryption-keys.md @@ -2,7 +2,7 @@ Kubernetes stores a variety of data including cluster state, application configurations, and secrets. Kubernetes supports the ability to [encrypt](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data) cluster data at rest. -In this lab you will generate an encryption key and an [encryption config](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#understanding-the-encryption-at-rest-configuration) suitable for encrypting Kubernetes Secrets. +In this chapter, you will generate an encryption key and an [encryption config](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#understanding-the-encryption-at-rest-configuration) suitable for encrypting Kubernetes Secrets. ## The Encryption Key @@ -32,7 +32,7 @@ resources: EOF ``` -Copy the `encryption-config.yaml` encryption config file to each controller instance: +Copy the `encryption-config.yaml` encryption config file to each controller node: ``` $ USERNAME=