From e600b686846233f2e5de5d638aa017f87b9f7e7b Mon Sep 17 00:00:00 2001 From: Daniel Hougaard <62331820+DanielHougaard@users.noreply.github.com> Date: Thu, 13 Jun 2024 22:15:57 +0200 Subject: [PATCH] Docs: Updated kubernetes --- docs/integrations/platforms/kubernetes.mdx | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/integrations/platforms/kubernetes.mdx b/docs/integrations/platforms/kubernetes.mdx index 4a68f7365..e9cb548e9 100644 --- a/docs/integrations/platforms/kubernetes.mdx +++ b/docs/integrations/platforms/kubernetes.mdx @@ -98,7 +98,9 @@ spec: # Native Kubernetes Auth kubernetesAuth: identityId: - serviceAccountTokenPath: "/path/to/your/service-account/token" # Optional, defaults to /var/run/secrets/kubernetes.io/serviceaccount/token + serviceAccountRef: + name: + namespace: # secretsScope is identical to the secrets scope in the universalAuth field in this sample. secretsScope: @@ -257,6 +259,11 @@ spec: Once you have created your machine identity and added it to your project(s), you will need to add the identity ID to your InfisicalSecret resource. In the `authentication.kubernetesAuth.identityId` field, add the identity ID of the machine identity you created. See the example below for more details. + + When you configured your Kubernetes machine identity, you would have created a service account token if you followed the [Kubernetes machine identity guide](/documentation/platform/identities/kubernetes-auth). If you did not create a service account token, please follow the guide to do so. + + You will need to enter the name of the service account and the namespace where the service account lives. The example below shows how to add the service account token to the InfisicalSecret resource. + @@ -278,7 +285,9 @@ spec: authentication: kubernetesAuth: identityId: - serviceAccountTokenPath: "/path/to/your/service-account/token" # Optional, defaults to /var/run/secrets/kubernetes.io/serviceaccount/token + serviceAccountRef: + name: + namespace: # secretsScope is identical to the secrets scope in the universalAuth field in this sample. secretsScope: