Support for HashiCorp Vault Secrets in VectorPipeline

[Enorshionari]

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.

[aa1ex]

Hello!

We haven’t planned to add HashiCorp Vault support in the near future. However, in the latest version of the vector-operator, we have introduced the ability to import variables from a Secret using secretRef. You can find more details in the documentation here.

Let us know if you have any questions!

[username-here10]

we have introduced the ability to import variables from a Secret using secretRef. You can find more details in the documentation here.

I am interested in installing a single vector daemonset on the cluster and letting developers define their own vectorPipelines CRs in order to have "log collection as a service".

Defining the credentials in the vector CR would require developers to send me their secrets and it would allow different developers to access each other's credentials in the vectorPipeline.

I think the proposal to inject secrets through the vectorPipeline CR is a good idea.

[aa1ex]

Hi! We have started implementing the ability to inject secrets via vectorPipeline. It will be done using the standard Vector mechanism. I’ll post updates in this thread as soon as there are any.