From f77b3993b9003cdf8d341d88605d7e667005c929 Mon Sep 17 00:00:00 2001 From: Rita Zhang Date: Mon, 28 Oct 2024 08:01:33 -0700 Subject: [PATCH] deprecate EnforceMountableSecretsAnnotation in 1.32 Signed-off-by: Rita Zhang Kubernetes-commit: e7cdc595551954d6b87a859296eb09fddd01f3c9 --- openapi/openapitest/testdata/api__v1_openapi.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openapi/openapitest/testdata/api__v1_openapi.json b/openapi/openapitest/testdata/api__v1_openapi.json index 4637e313..c7126701 100644 --- a/openapi/openapitest/testdata/api__v1_openapi.json +++ b/openapi/openapitest/testdata/api__v1_openapi.json @@ -6851,7 +6851,7 @@ "description": "Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata" }, "secrets": { - "description": "Secrets is a list of the secrets in the same namespace that pods running using this ServiceAccount are allowed to use. Pods are only limited to this list if this service account has a \"kubernetes.io/enforce-mountable-secrets\" annotation set to \"true\". This field should not be used to find auto-generated service account token secrets for use outside of pods. Instead, tokens can be requested directly using the TokenRequest API, or service account token secrets can be manually created. More info: https://kubernetes.io/docs/concepts/configuration/secret", + "description": "Secrets is a list of the secrets in the same namespace that pods running using this ServiceAccount are allowed to use. Pods are only limited to this list if this service account has a \"kubernetes.io/enforce-mountable-secrets\" annotation set to \"true\". The \"kubernetes.io/enforce-mountable-secrets\" annotation is deprecated since v1.32. Prefer separate namespaces to isolate access to mounted secrets. This field should not be used to find auto-generated service account token secrets for use outside of pods. Instead, tokens can be requested directly using the TokenRequest API, or service account token secrets can be manually created. More info: https://kubernetes.io/docs/concepts/configuration/secret", "items": { "allOf": [ {