Skip to content

Commit ada845e

Browse files
author
Tim Bannister
committed
Link to KMS setup doc
1 parent 9f8b35d commit ada845e

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

content/en/docs/tasks/administer-cluster/encrypt-data.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -323,20 +323,21 @@ appropriate for your security needs.
323323

324324
## Encrypt your data {#encrypting-your-data}
325325

326+
### Generate the encryption key {#generate-key-no-kms}
327+
326328
{{< caution >}}
327329
Storing the raw encryption key in the EncryptionConfig only moderately improves your security posture,
328330
compared to no encryption.
329331

330332
For additional secrecy, consider using the `kms` provider as this relies on keys held outside your
331333
Kubernetes cluster. Implementations of `kms` can work with hardware security modules or with
332334
encryption services managed by your cloud provider.
333-
{{< /caution >}}
334335

335-
### Generate the encryption key {#generate-key-no-kms}
336-
337-
_These instructions explain how to set up non-KMS encryption. You can use these as a guide
338-
to how you would configure KMS encryption; however, the specific details of that depend
339-
on the (external) KMS integration that you are using._
336+
To learn about setting
337+
up encryption at rest using KMS, see
338+
[Using a KMS provider for data encryption](/docs/tasks/administer-cluster/kms-provider/).
339+
The KMS provider plugin that you use may also come with additional specific documentation.
340+
{{< /caution >}}
340341

341342
Start by generating a new encryption key, and then encode it using base64:
342343

0 commit comments

Comments
 (0)