You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when working with the Vector logging operator within kind: Vectorpipeline, we face a limitation in handling credentials. While we store credentials directly in the Vector Custom Resource Definition (CRD), the VectorPipeline configuration references these credentials through variable links.
We suggest integrating support for HashiCorp Vault to manage secrets in a more secure and efficient manner within the VectorPipeline configuration. This enhancement should allow the use of Vault secrets directly within kind: Vectorpipeline.
Strengthened security through centralized secret management.
Elimination of hardcoded sensitive information in CRDs.
Alignment with best practices for managing confidential data.
The text was updated successfully, but these errors were encountered:
Currently, when working with the Vector logging operator within kind: Vectorpipeline, we face a limitation in handling credentials. While we store credentials directly in the Vector Custom Resource Definition (CRD), the VectorPipeline configuration references these credentials through variable links.
We suggest integrating support for HashiCorp Vault to manage secrets in a more secure and efficient manner within the VectorPipeline configuration. This enhancement should allow the use of Vault secrets directly within kind: Vectorpipeline.
The text was updated successfully, but these errors were encountered: