awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-08 11:27:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

modify verify step in docs

Browse Source
This commit is contained in:
Maidul Islam
2022-12-17 23:57:06 -05:00
parent cd59ca745d
commit 19b909cd12
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/platforms/kubernetes.mdx
+3 -2
View File
@@ -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. Once the secret is created, add the name and namespace of the secret under `tokenSecretReference` field in the InfisicalSecret custom resource.
{' '} {' '}
<Info> <Info>
No matter what the name of the secret is or its namespace, it must contain a 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 key named `infisicalToken` with a valid Infisical Token as the value
@@ -98,8 +99,8 @@ spec:
## Verify ## 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 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 confirm that the operator has created the managed secret specified in managedSecretReference, you can list the secrets in the namespace you specified. To verify that the operator has successfully created the managed secret, you can check the secrets in the namespace that was specified.
```bash ```bash
# Verify managed secret is created # Verify managed secret is created