From 04a9604ba94a266edc95111a1c774d47a2c4f6a3 Mon Sep 17 00:00:00 2001 From: Maidul Islam Date: Thu, 27 Apr 2023 11:14:47 -0400 Subject: [PATCH] add advanced use cases for hostAPI --- docs/integrations/platforms/kubernetes.mdx | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/docs/integrations/platforms/kubernetes.mdx b/docs/integrations/platforms/kubernetes.mdx index eb58a36c5..efe5297ad 100644 --- a/docs/integrations/platforms/kubernetes.mdx +++ b/docs/integrations/platforms/kubernetes.mdx @@ -71,11 +71,18 @@ spec: If you are fetching secrets from a self hosted instance of Infisical set the value of `hostAPI` to ` https://your-self-hosted-instace.com/api` - If you are self-hosting and want to access Infisical backend's service directly you can use a hostAPI configuration as below. - ``` bash - http://..svc.cluster.local:4000/api - ``` When `hostAPI` is not defined the operator fetches secrets from Infisical Cloud. + + + If you have installed your Infisical instance within the same cluster as the Infisical operator, you can optionally access the Infisical backend's service directly without having to route through the public internet. + To achieve this, use the following address for the hostAPI field: + + ``` bash + http://..svc.cluster.local:4000/api + ``` + + Make sure to replace `` and `` with the appropriate values for your backend service and namespace. +