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

fix typo

Browse Source
This commit is contained in:
Maidul Islam
2025-01-09 12:36:52 -05:00
parent 1639bda3f6
commit 325ce73b9f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/platforms/kubernetes/infisical-dynamic-secret-crd.mdx
+2 -2
View File
@@ -5,12 +5,12 @@ description: "Learn how to generate dynamic secret leases in Infisical and sync
--- ---
## Overview ## Overview
The **InfisicalDynamicSecret** CRD allows you to easily create and manage dynamic secret leases in Infisical and automatically syncing them to your Kubernetes cluster as native **Kubernetes Secret** resources. The **InfisicalDynamicSecret** CRD allows you to easily create and manage dynamic secret leases in Infisical and automatically sync them to your Kubernetes cluster as native **Kubernetes Secret** resources.
This means any Pod, Deployment, or other Kubernetes resource can make use of dynamic secrets from Infisical just like any other K8s secret. This means any Pod, Deployment, or other Kubernetes resource can make use of dynamic secrets from Infisical just like any other K8s secret.
This CRD offers the following features: This CRD offers the following features:
- **Generate a dynamic secret lease** in Infisical and track its lifecycle. - **Generate a dynamic secret lease** in Infisical and track its lifecycle.
- **write** the dynamic secret from Infisical to your cluster as native Kubernetes secret. - **Write** the dynamic secret from Infisical to your cluster as native Kubernetes secret.
- **Automatically rotate** the dyanmic secret value before it expires to make sure your cluster always has valid credentials. - **Automatically rotate** the dyanmic secret value before it expires to make sure your cluster always has valid credentials.
- **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.