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

docs: docs for ID and slug support across all operator CRDS

Browse Source
This commit is contained in:
Daniel Hougaard
2025-09-05 14:15:27 +02:00
parent b53c250ded
commit e9c14d0c0f
3 changed files with 50 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx
+21 -6
View File
@@ -142,7 +142,10 @@ spec:
authentication:
universalAuth:
secretsScope:
# either projectSlug or projectId is required
projectSlug: <project-slug> # <-- project slug
projectId: <project-id> # <-- project id
envSlug: <env-slug> # "dev", "staging", "prod", etc..
secretsPath: "<secrets-path>" # Root is "/"
credentialsRef:
@@ -496,9 +499,11 @@ spec:
<Info>
Make sure to also populate the `secretsScope` field with the project slug
_`projectSlug`_, environment slug _`envSlug`_, and secrets path
_`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
_`secretsPath`_ that you want to fetch secrets from. Please see the example
below.
Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
</Info>
## Example
@@ -545,9 +550,11 @@ spec:
<Info>
Make sure to also populate the `secretsScope` field with the project slug
_`projectSlug`_, environment slug _`envSlug`_, and secrets path
_`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
_`secretsPath`_ that you want to fetch secrets from. Please see the example
below.
Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
</Info>
## Example
@@ -588,9 +595,11 @@ spec:
<Info>
Make sure to also populate the `secretsScope` field with the project slug
_`projectSlug`_, environment slug _`envSlug`_, and secrets path
_`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
_`secretsPath`_ that you want to fetch secrets from. Please see the example
below.
Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
</Info>
## Example
@@ -631,9 +640,11 @@ spec:
<Info>
Make sure to also populate the `secretsScope` field with the project slug
_`projectSlug`_, environment slug _`envSlug`_, and secrets path
_`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
_`secretsPath`_ that you want to fetch secrets from. Please see the example
below.
Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
</Info>
## Example
@@ -675,9 +686,11 @@ spec:
<Info>
Make sure to also populate the `secretsScope` field with the project slug
_`projectSlug`_, environment slug _`envSlug`_, and secrets path
_`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
_`secretsPath`_ that you want to fetch secrets from. Please see the example
below.
Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
</Info>
## Example
@@ -730,9 +743,11 @@ spec:
<Info>
Make sure to also populate the `secretsScope` field with the project slug
_`projectSlug`_, environment slug _`envSlug`_, and secrets path
_`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
_`secretsPath`_ that you want to fetch secrets from. Please see the example
below.
Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
</Info>
## Example