From 19b909cd1254399986ff43709959321fefa62b66 Mon Sep 17 00:00:00 2001 From: Maidul Islam Date: Sat, 17 Dec 2022 23:57:06 -0500 Subject: [PATCH] modify verify step in docs --- docs/integrations/platforms/kubernetes.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/integrations/platforms/kubernetes.mdx b/docs/integrations/platforms/kubernetes.mdx index a43f03824..51a9d7ec4 100644 --- a/docs/integrations/platforms/kubernetes.mdx +++ b/docs/integrations/platforms/kubernetes.mdx @@ -50,6 +50,7 @@ This resource is available after installing the Infisical operator. In order to Once the secret is created, add the name and namespace of the secret under `tokenSecretReference` field in the InfisicalSecret custom resource. {' '} + No matter what the name of the secret is or its namespace, it must contain a key named `infisicalToken` with a valid Infisical Token as the value @@ -98,8 +99,8 @@ spec: ## Verify -After creating an `InfisicalSecret` custom resource, you can reference the managed secret specified in the `managedSecretReference` field in your deployment just like any other Kubernetes secret. -To confirm that the operator has created the managed secret specified in managedSecretReference, you can list the secrets in the namespace you specified. +To use the InfisicalSecret custom resource in your deployment, you can simply reference the managed secret specified in the `managedSecretReference` field as you would any other Kubernetes secret. +To verify that the operator has successfully created the managed secret, you can check the secrets in the namespace that was specified. ```bash # Verify managed secret is created