From 9b31a7bbb107143bb13b2df84dafcc743cff52ab Mon Sep 17 00:00:00 2001 From: Sheen Capadngan Date: Fri, 29 Nov 2024 22:13:47 +0800 Subject: [PATCH] misc: added important note --- docs/integrations/platforms/kubernetes-csi.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/integrations/platforms/kubernetes-csi.mdx b/docs/integrations/platforms/kubernetes-csi.mdx index 79cfba304..08f4ae237 100644 --- a/docs/integrations/platforms/kubernetes-csi.mdx +++ b/docs/integrations/platforms/kubernetes-csi.mdx @@ -106,6 +106,12 @@ In order for the Infisical CSI provider to pull secrets from your Infisical proj a machine identity with [Kubernetes authentication](https://infisical.com/docs/documentation/platform/identities/kubernetes-auth) configured with your cluster. You can refer to the documentation for setting it up [here](https://infisical.com/docs/documentation/platform/identities/kubernetes-auth#guide). + + The allowed audience field of the Kubernetes authentication settings should + match the audience specified for the Secrets Store CSI driver during + installation. + + ### Creating Secret Provider Class With the Secrets Store CSI driver and the Infisical CSI provider installed, create a Kubernetes [SecretProviderClass](https://secrets-store-csi-driver.sigs.k8s.io/concepts.html#secretproviderclass) resource to establish