awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-09-22 13:39:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: better k8s pre-req

Browse Source
This commit is contained in:
Daniel Hougaard
2025-01-10 20:16:30 +01:00
parent 13894261ce
commit 956fb2efb4
2 changed files with 12 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/integrations/platforms/kubernetes/infisical-dynamic-secret-crd.mdx
View File

@@ -15,8 +15,10 @@ This CRD offers the following features:
- **Optionally trigger redeployments** of any workloads that consume the secret if you enable auto-reload.
### Prerequisites
- The operator is installed on to your Kubernetes cluster
- You have already configured a dynamic secret in Infisical
- A project within Infisical.
- A [machine identity](/docs/documentation/platform/identities/overview) ready for use in Infisical that has permissions to create dynamic secret leases in the project.
- You have already configured a dynamic secret in Infisical.
- The operator is installed on to your Kubernetes cluster.
## Configure Dynamic Secret CRD

11
docs/integrations/platforms/kubernetes/infisical-push-secret-crd.mdx
View File

@@ -15,8 +15,13 @@ This CRD offers the following features:
- **Create Secrets** in Infisical and manage its lifecycle.
- **Automatic secret deletion** when the InfisicalPushSecret CRD is deleted.
### Prerequisites
### Example usage
- A project within Infisical.
- A [machine identity](/docs/documentation/platform/identities/overview) ready for use in Infisical that has permissions to create secrets in your project.
- The operator is installed on to your Kubernetes cluster.
## Example usage
Below is a sample InfisicalPushSecret CRD that pushes secrets defined in a Kubernetes secret to Infisical.
@@ -97,7 +102,7 @@ After applying the soruce-secret.yaml file, you are ready to apply the Infisical
After applying the InfisicalPushSecret CRD, you should notice that the secrets you have defined in your source-secret.yaml file have been pushed to your specified destination in Infisical.
### InfisicalPushSecret CRD properties
## InfisicalPushSecret CRD properties
<Accordion title="hostAPI">
If you are fetching secrets from a self-hosted instance of Infisical set the value of `hostAPI` to
@@ -397,7 +402,7 @@ After applying the InfisicalPushSecret CRD, you should notice that the secrets y
</Accordion>
### Applying the InfisicalPushSecret CRD to your cluster
## Applying the InfisicalPushSecret CRD to your cluster
Once you have configured the `InfisicalPushSecret` CRD with the required fields, you can apply it to your cluster.
After applying, you should notice that the secrets have been pushed to Infisical.