From e8d6c920a02e142ebd825044fb3a368ffd7a7379 Mon Sep 17 00:00:00 2001
From: Daniel Hougaard <daniel@infisical.com>
Date: Thu, 30 Oct 2025 20:08:06 +0400
Subject: [PATCH] Update overview.mdx

Update overview.mdx
---
 .../platforms/kubernetes/overview.mdx         | 46 +++++++++++++++++++
 1 file changed, 46 insertions(+)

diff --git a/docs/integrations/platforms/kubernetes/overview.mdx b/docs/integrations/platforms/kubernetes/overview.mdx
index ce9afcced..7a381d996 100644
--- a/docs/integrations/platforms/kubernetes/overview.mdx
+++ b/docs/integrations/platforms/kubernetes/overview.mdx
@@ -41,6 +41,29 @@ If you require stronger isolation and stricter access controls, a namespace-scop
     ```bash
     helm install --generate-name infisical-helm-charts/secrets-operator
     ```
+
+    <Accordion title="Using your own service account">
+      By default a service account is created for the operator based on the operator release name.
+      You can bring your own service account by setting `controllerManager.serviceAccount.create` to `false` and setting `controllerManager.serviceAccount.name` to the name of the service account you want to use in your values.yaml file.
+
+      Example values.yaml file:
+
+      ```yaml values.yaml
+      controllerManager:
+        serviceAccount:
+          create: false
+          name: my-service-account
+      # other values...
+      ```
+
+      <Note>
+        Please note that if you set `controllerManager.serviceAccount.create` to `false`, the service account needs to already exist in the namespace you are installing the operator in.
+      </Note>
+
+      <Tip>
+        Custom service accounts are supported in chart version `0.10.11` and above. Please upgrade your helm chart to `0.10.11` or above before attempting to use custom service accounts.
+      </Tip>
+    </Accordion>
   </Tab>
   <Tab title="Namespace Scoped Installation">
     The operator can be configured to watch and manage secrets in a specific namespace instead of having cluster-wide access. This is useful for:
@@ -67,6 +90,29 @@ If you require stronger isolation and stricter access controls, a namespace-scop
       --set installCRDs=false
     ```
 
+    <Accordion title="Using your own service account">
+      By default a service account is created for the operator based on the operator release name.
+      You can bring your own service account by setting `controllerManager.serviceAccount.create` to `false` and setting `controllerManager.serviceAccount.name` to the name of the service account you want to use in your values.yaml file.
+
+      Example values.yaml file:
+
+      ```yaml values.yaml
+      controllerManager:
+        serviceAccount:
+          create: false
+          name: my-service-account
+      # other values...
+      ```
+
+      <Note>
+        Please note that if you set `controllerManager.serviceAccount.create` to `false`, the service account needs to already exist in the namespace you are installing the operator in.
+      </Note>
+
+      <Tip>
+        Custom service accounts are supported in chart version `0.10.11` and above. Please upgrade your helm chart to `0.10.11` or above before attempting to use custom service accounts.
+      </Tip>
+    </Accordion>
+
     When scoped to a namespace, the operator will:
 
     - Only watch InfisicalSecrets in the specified namespace