> ## Documentation Index > Fetch the complete documentation index at: https://infisical-devin-1781641701-docs-github-pat-fine-grained.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Kubernetes CSI > How to use the Infisical Kubernetes CSI provider to inject secrets directly into Kubernetes pods. ## Overview The Infisical CSI provider allows you to use Infisical with the [Secrets Store CSI driver](https://secrets-store-csi-driver.sigs.k8s.io) to inject secrets directly into your Kubernetes pods through a volume mount. In contrast to the [Infisical Kubernetes Operator](https://infisical.com/docs/integrations/platforms/kubernetes), the Infisical CSI provider will allow you to sync Infisical secrets directly to pods as files, removing the need for Kubernetes secret resources. ```mermaid theme={null} flowchart LR subgraph Secrets Management SS(Infisical) --> CSP(Infisical CSI Provider) CSP --> CSD(Secrets Store CSI Driver) end subgraph Pod CSD --> V(Volume) V <--> P(Application) end ``` ## Features The following features are supported by the Infisical CSI Provider: * Integration with Secrets Store CSI Driver for direct pod mounting * Authentication using Kubernetes service accounts via machine identities * Auto-syncing secrets when enabled via CSI Driver * Configurable secret paths and file mounting locations * Installation via Helm ## Prerequisites The Infisical CSI provider is only supported for Kubernetes clusters with version >= 1.20. ## Limitations Currently, the Infisical CSI provider only supports static secrets. ## Deploy to Kubernetes cluster ### Install Secrets Store CSI Driver In order to use the Infisical CSI provider, you will first have to install the [Secrets Store CSI driver](https://secrets-store-csi-driver.sigs.k8s.io/getting-started/installation) to your cluster. #### Standard Installation For most Kubernetes clusters, use the following installation: ```bash theme={null} helm repo add secrets-store-csi-driver https://kubernetes-sigs.github.io/secrets-store-csi-driver/charts ``` ```bash theme={null} helm install csi secrets-store-csi-driver/secrets-store-csi-driver \ --namespace=kube-system \ --set "tokenRequests[0].audience=infisical" \ --set enableSecretRotation=true \ --set rotationPollInterval=2m \ --set "syncSecret.enabled=true" \ ``` The flags configure the following: * `tokenRequests[0].audience=infisical`: Sets the audience value for service account token authentication (recommended for environments that support custom audiences) * `enableSecretRotation=true`: Enables automatic secret updates from Infisical * `rotationPollInterval=2m`: Checks for secret updates every 2 minutes * `syncSecret.enabled=true`: Enables syncing secrets to Kubernetes secrets If you do not wish to use the auto-syncing feature of the secrets store CSI driver, you can omit the `enableSecretRotation` and the `rotationPollInterval` flags. Do note that by default, secrets from Infisical are only fetched and mounted during pod creation. If there are any changes made to the secrets in Infisical, they will not propagate to the pods unless auto-syncing is enabled for the CSI driver. #### Installation for Environments Without Custom Audience Support Some Kubernetes environments (such as AWS EKS) don't support custom audiences and will reject tokens with non-default audiences. For these environments, use this installation instead: ```bash theme={null} helm install csi secrets-store-csi-driver/secrets-store-csi-driver \ --namespace=kube-system \ --set enableSecretRotation=true \ --set rotationPollInterval=2m \ --set "syncSecret.enabled=true" \ ``` **Environments without custom audience support**: Do not set a custom audience when installing the CSI driver in environments that reject custom audiences. Instead, use the installation above and set `useDefaultAudience: "true"` in your SecretProviderClass configuration. ### Install Infisical CSI Provider You would then have to install the Infisical CSI provider to your cluster. **Install the latest Infisical Helm repository** ```bash theme={null} helm repo add infisical-helm-charts 'https://dl.cloudsmith.io/public/infisical/helm-charts/helm/charts/' helm repo update ``` **Install the Helm Chart** ```bash theme={null} helm install infisical-csi-provider infisical-helm-charts/infisical-csi-provider ``` For a list of all supported arguments for the helm installation, you can run the following: ```bash theme={null} helm show values infisical-helm-charts/infisical-csi-provider ``` ### Authentication In order for the Infisical CSI provider to pull secrets from your Infisical project, you will have to configure 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). **Important**: The "Allowed Audience" field in your machine identity's Kubernetes authentication settings must match your CSI driver installation. If you used the standard installation with `tokenRequests[0].audience=infisical`, set the "Allowed Audience" field to `infisical`. If you used the installation for environments without custom audience support, leave the "Allowed Audience" field empty. ### 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 the connection between the CSI driver and the Infisical CSI provider for secret retrieval. You can create as many Secret Provider Classes as needed for your cluster. #### Standard Configuration ```yaml theme={null} apiVersion: secrets-store.csi.x-k8s.io/v1 kind: SecretProviderClass metadata: name: my-infisical-app-csi-provider spec: provider: infisical parameters: infisicalUrl: "https://app.infisical.com" authMethod: "kubernetes" identityId: "ad2f8c67-cbe2-417a-b5eb-1339776ec0b3" projectId: "09eda1f8-85a3-47a9-8a6f-e27f133b2a36" envSlug: "prod" secrets: | - secretPath: "/" fileName: "dbPassword" secretKey: "DB_PASSWORD" - secretPath: "/app" fileName: "appSecret" secretKey: "APP_SECRET" ``` #### Configuration for Environments Without Custom Audience Support For environments that don't support custom audiences (such as AWS EKS), use this configuration instead: ```yaml theme={null} apiVersion: secrets-store.csi.x-k8s.io/v1 kind: SecretProviderClass metadata: name: my-infisical-app-csi-provider spec: provider: infisical parameters: infisicalUrl: "https://app.infisical.com" authMethod: "kubernetes" useDefaultAudience: "true" identityId: "ad2f8c67-cbe2-417a-b5eb-1339776ec0b3" projectId: "09eda1f8-85a3-47a9-8a6f-e27f133b2a36" envSlug: "prod" secrets: | - secretPath: "/" fileName: "dbPassword" secretKey: "DB_PASSWORD" - secretPath: "/app" fileName: "appSecret" secretKey: "APP_SECRET" ``` **Key difference**: The only change from the standard configuration is the addition of `useDefaultAudience: "true"`. This parameter tells the CSI provider to use the default Kubernetes audience instead of a custom "infisical" audience, which is required for environments that reject custom audiences. The SecretProviderClass should be provisioned in the same namespace as the pod you intend to mount secrets to. #### Supported Parameters The base URL of your Infisical instance. If you're using Infisical Cloud US, this should be set to `https://app.infisical.com`. If you're using Infisical Cloud EU, then this should be set to `https://eu.infisical.com`. The CA certificate of the Infisical instance in order to establish SSL/TLS when the instance uses a private or self-signed certificate. Unless necessary, this should be omitted. The auth method to use for authenticating the Infisical CSI provider with Infisical. For now, the only supported method is `kubernetes`. The ID of the machine identity to use for authenticating the Infisical CSI provider with your Infisical organization. This should be the machine identity configured with Kubernetes authentication. The project ID of the Infisical project to pull secrets from. The slug of the project environment to pull secrets from. An array that defines which secrets to retrieve and how to mount them. Each entry requires three properties: `secretPath` and `secretKey` work together to identify the source secret to fetch, while `fileName` specifies the path where the secret's value will be mounted within the pod's filesystem. The custom audience value configured for the CSI driver. This defaults to `infisical`. When set to `"true"`, the Infisical CSI provider will use the default Kubernetes audience instead of a custom audience. This is required for environments that don't support custom audiences (such as AWS EKS), which reject tokens with non-default audiences. When using this option, do not set a custom audience in the CSI driver installation. This defaults to `false`. When enabled, the CSI provider will dynamically create service account tokens on-demand using the default Kubernetes audience, rather than using pre-existing tokens from the CSI driver. ### Using Secret Provider Class A pod can use the Secret Provider Class by mounting it as a CSI volume: ```yaml theme={null} apiVersion: v1 kind: Pod metadata: name: nginx-secrets-store labels: app: nginx spec: containers: - name: nginx image: nginx volumeMounts: - name: secrets-store-inline mountPath: "/mnt/secrets-store" readOnly: true volumes: - name: secrets-store-inline csi: driver: secrets-store.csi.k8s.io readOnly: true volumeAttributes: secretProviderClass: "my-infisical-app-csi-provider" ``` When the pod is created, the secrets are mounted as individual files in the /mnt/secrets-store directory. ### Verifying Secret Mounts To verify your secrets are mounted correctly: ```bash theme={null} # Check pod status kubectl get pod nginx-secrets-store # View mounted secrets kubectl exec -it nginx-secrets-store -- ls -l /mnt/secrets-store ``` ### Troubleshooting To troubleshoot issues with the Infisical CSI provider, refer to the logs of the Infisical CSI provider running on the same node as your pod. ```bash theme={null} kubectl logs infisical-csi-provider-7x44t ``` You can also refer to the logs of the secrets store CSI driver. Modify the command below with the appropriate pod and namespace of your secrets store CSI driver installation. ```bash theme={null} kubectl logs csi-secrets-store-csi-driver-7h4jp -n=kube-system ``` **Common issues include:** * Mismatch in the audience value of the CSI driver with the machine identity's Kubernetes auth configuration * SecretProviderClass in the wrong namespace * Invalid machine identity configuration * Incorrect secret paths or keys **Issues in environments without custom audience support:** * **Token authentication failed with custom audience**: If you're seeing authentication errors in environments that don't support custom audiences (such as AWS EKS), ensure you're using the installation without custom audience and have set `useDefaultAudience: "true"` in your SecretProviderClass * **Audience not allowed errors**: Make sure the "Allowed Audience" field is left empty in your machine identity's Kubernetes authentication configuration when using environments that don't support custom audiences ## Best Practices For additional guidance on setting this up for your production cluster, you can refer to the Secrets Store CSI driver documentation [here](https://secrets-store-csi-driver.sigs.k8s.io/topics/best-practices). ## Frequently Asked Questions Yes, but it requires an indirect approach: 1. First enable syncing to Kubernetes secrets by setting `syncSecret.enabled=true` in the CSI driver installation 2. Configure the Secret Provider Class to sync specific secrets to Kubernetes secrets 3. Use the resulting Kubernetes secrets in your pod's environment variables This means secrets are first synced to Kubernetes secrets before they can be used as environment variables. You can find detailed examples in the [Secrets Store CSI driver documentation](https://secrets-store-csi-driver.sigs.k8s.io/topics/set-as-env-var). Yes, you will need to explicitly list each secret you want to sync in the Secret Provider Class configuration. This is a common requirement across all CSI providers as the Secrets Store CSI Driver architecture requires specific mapping of secrets to their mounted file locations.