From 28dc3a4b1ced3c74c6050e87e4b1113f5ba10167 Mon Sep 17 00:00:00 2001
From: Maidul Islam <maidul98@gmail.com>
Date: Fri, 12 Apr 2024 12:49:45 -0400
Subject: [PATCH] add docs for owner policy

---
 docs/integrations/platforms/kubernetes.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/docs/integrations/platforms/kubernetes.mdx b/docs/integrations/platforms/kubernetes.mdx
index 29ca9c4ba..099adc64c 100644
--- a/docs/integrations/platforms/kubernetes.mdx
+++ b/docs/integrations/platforms/kubernetes.mdx
@@ -92,6 +92,7 @@ spec:
     managedSecretReference:
         secretName: managed-secret
         secretNamespace: default
+        creationPolicy: "Orphan" ## Owner | Orphan (default)
         # secretType: kubernetes.io/dockerconfigjson
 ```
 ### InfisicalSecret CRD properties
@@ -232,6 +233,19 @@ The namespace of the managed Kubernetes secret to be created.
 </Accordion>
 <Accordion title="managedSecretReference.secretType">
 Override the default Opaque type for managed secrets with this field. Useful for creating kubernetes.io/dockerconfigjson secrets.
+</Accordion>
+<Accordion title="managedSecretReference.creationPolicy">
+Creation polices allow you to control whether or not to owner references should be added to the managed Kubernetes secret that is generated by the Infisical operator. 
+This is useful for tools such as ArgoCD, where every resource requires an owner reference; otherwise, it will be pruned automatically.
+
+#### Available options 
+- `Orphan` (default)
+- `Owner`
+
+<Tip>
+  When creation policy is set to `Owner`, the `InfisicalSecret` CRD must be in the same namespace as where the managed kubernetes secret. 
+</Tip>
+
 </Accordion>
 
 ### Propagating labels & annotations