docs: better k8s pre-req

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

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. - **Optionally trigger redeployments** of any workloads that consume the secret if you enable auto-reload.
### Prerequisites ### Prerequisites
- The operator is installed on to your Kubernetes cluster - A project within Infisical.
- You have already configured a dynamic secret in 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 ## Configure Dynamic Secret CRD

View File

@@ -15,8 +15,13 @@ This CRD offers the following features:
- **Create Secrets** in Infisical and manage its lifecycle. - **Create Secrets** in Infisical and manage its lifecycle.
- **Automatic secret deletion** when the InfisicalPushSecret CRD is deleted. - **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. 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. 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"> <Accordion title="hostAPI">
If you are fetching secrets from a self-hosted instance of Infisical set the value of `hostAPI` to 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> </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. 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. After applying, you should notice that the secrets have been pushed to Infisical.