File tree Expand file tree Collapse file tree 1 file changed +7
-6
lines changed
content/en/docs/tasks/administer-cluster Expand file tree Collapse file tree 1 file changed +7
-6
lines changed Original file line number Diff line number Diff line change @@ -323,20 +323,21 @@ appropriate for your security needs.
323
323
324
324
# # Encrypt your data {#encrypting-your-data}
325
325
326
+ # ## Generate the encryption key {#generate-key-no-kms}
327
+
326
328
{{< caution >}}
327
329
Storing the raw encryption key in the EncryptionConfig only moderately improves your security posture,
328
330
compared to no encryption.
329
331
330
332
For additional secrecy, consider using the `kms` provider as this relies on keys held outside your
331
333
Kubernetes cluster. Implementations of `kms` can work with hardware security modules or with
332
334
encryption services managed by your cloud provider.
333
- {{< /caution >}}
334
335
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 >}}
340
341
341
342
Start by generating a new encryption key, and then encode it using base64 :
342
343
You can’t perform that action at this time.
0 commit comments