From 443b8f747bb5b105aadce0487dc7e478a56120eb Mon Sep 17 00:00:00 2001 From: Maidul Islam Date: Thu, 29 Feb 2024 17:54:53 -0500 Subject: [PATCH] Update kubernetes-helm.mdx --- .../deployment-options/kubernetes-helm.mdx | 37 +++++++++++-------- 1 file changed, 22 insertions(+), 15 deletions(-) diff --git a/docs/self-hosting/deployment-options/kubernetes-helm.mdx b/docs/self-hosting/deployment-options/kubernetes-helm.mdx index 300cb3db9..e1a45f408 100644 --- a/docs/self-hosting/deployment-options/kubernetes-helm.mdx +++ b/docs/self-hosting/deployment-options/kubernetes-helm.mdx @@ -47,26 +47,33 @@ description: "Use Helm chart to install Infisical on your Kubernetes cluster" For test or proof-of-concept purposes, you may omit `DB_CONNECTION_URI` and `REDIS_URL` from `infisical-secrets`. This is because the Helm chart will automatically provision and connect to the in-cluster instances of Postgres and Redis by default. - + ```yaml simple-values-example.yaml + apiVersion: v1 + kind: Secret + metadata: + name: infisical-secrets + type: Opaque + stringData: + AUTH_SECRET: <> + ENCRYPTION_KEY: <> + ``` For production environments, we recommend using Cloud-based Platform as a Service (PaaS) solutions for PostgreSQL and Redis to ensure high availability. In on-premise setups, it's recommended to configure Redis and Postgres for high availability, either by using Bitnami charts or a custom configuration. - + ```yaml simple-values-example.yaml + apiVersion: v1 + kind: Secret + metadata: + name: infisical-secrets + type: Opaque + stringData: + AUTH_SECRET: <> + ENCRYPTION_KEY: <> + REDIS_URL: <> + DB_CONNECTION_URI: <> + ``` - - ```yaml simple-values-example.yaml - apiVersion: v1 - kind: Secret - metadata: - name: infisical-secrets - type: Opaque - stringData: - AUTH_SECRET: <> - ENCRYPTION_KEY: <> - REDIS_URL: <> - DB_CONNECTION_URI: <> - ```