From 94c0d783b8bca7f5c466bd8e6a98b8e999642e33 Mon Sep 17 00:00:00 2001 From: Austin Workman Date: Thu, 14 Mar 2024 17:11:47 -0500 Subject: [PATCH] K8s v1 Multiport documentation indentation updates (#20858) Fixing indentation in service account token secrets and addingn clarity about how they are used. Co-authored-by: David Yu --- website/content/docs/k8s/connect/index.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/content/docs/k8s/connect/index.mdx b/website/content/docs/k8s/connect/index.mdx index e2792e2bbe..0f320d3437 100644 --- a/website/content/docs/k8s/connect/index.mdx +++ b/website/content/docs/k8s/connect/index.mdx @@ -343,7 +343,7 @@ spec: `9090` and will also select the same pods. ~> Kubernetes 1.24+ only -In Kubernetes 1.24+ you need to [create a Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/#service-account-token-secrets) for each multi-port service that references the ServiceAccount, and the Kubernetes secret must have the same name as the ServiceAccount: +In Kubernetes 1.24+ you need to [create a Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/#service-account-token-secrets) for each additional Consul service associated with the pod in order to expose the Kubernetes ServiceAccount token to the Consul dataplane container running under the pod serviceAccount. The Kubernetes secret name must match the ServiceAccount name: @@ -354,7 +354,7 @@ metadata: name: web annotations: kubernetes.io/service-account.name: web - type: kubernetes.io/service-account-token +type: kubernetes.io/service-account-token --- apiVersion: v1 kind: Secret @@ -362,7 +362,7 @@ metadata: name: web-admin annotations: kubernetes.io/service-account.name: web-admin - type: kubernetes.io/service-account-token +type: kubernetes.io/service-account-token ```