From 3b306af95f9785f5eeec40d313707043d46a834d Mon Sep 17 00:00:00 2001 From: Paul Renault Date: Thu, 7 Dec 2023 16:12:15 +0100 Subject: [PATCH] Fix typo in TLS Secrets part --- content/en/docs/concepts/configuration/secret.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md index 36aea75968..19389f6c6f 100644 --- a/content/en/docs/concepts/configuration/secret.md +++ b/content/en/docs/concepts/configuration/secret.md @@ -381,7 +381,7 @@ The following YAML contains an example config for a TLS Secret: The TLS Secret type is provided only for convenience. You can create an `Opaque` type for credentials used for TLS authentication. -However, using the defined and public Secret type (`kubernetes.io/ssh-auth`) +However, using the defined and public Secret type (`kubernetes.io/tls`) helps ensure the consistency of Secret format in your project. The API server verifies if the required keys are set for a Secret of this type.