Skip to content

Kubernetes-secret operator #336

@LucasSegersFabro

Description

@LucasSegersFabro

Hey!

I love dot-env vault and I was wondering if there are any considerations for an auto sync solution for a kubernetes cluster.

Main use case:

  1. I manage my secrets with dotenv vault for many different applications and environments
  2. These applications run on a kubernetes cluster
  3. I'd like to keep any changes to a specific vault in sync with my cluster secrets and auto update my deployments

Something like external-secrets controller that has a well-stabilished API and implementations for different providers

Probably the controller would have to poll each configured secret for changes and pull them if needed, so maybe it's not something you'd want to enable for everyone at the same time (even though I guess that the majority of calls would be polling for the latest version)

Thanks :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions