A better way to manage secrets: reference an external secret defined in the cloud provider environment (please support the idea or give your feedback)

This page summarizes the projects mentioned and recommended in the original post on /r/kubernetes

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • kubernetes

    Production-Grade Container Scheduling and Management

  • secrets-store-csi-driver-provider-aws

    The AWS provider for the Secrets Store CSI Driver allows you to fetch secrets from AWS Secrets Manager and AWS Systems Manager Parameter Store, and mount them into Kubernetes pods.

  • AWS SS-CSI driver

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • secrets-store-csi-driver-provider-azure

    Azure Key Vault provider for Secret Store CSI driver allows you to get secret contents stored in Azure Key Vault instance and use the Secret Store CSI driver interface to mount them into Kubernetes pods.

  • Azure SS-CSI driver

  • secrets-store-csi-driver-provider-gcp

    Google Secret Manager provider for the Secret Store CSI Driver.

  • GCP SS-CSI driver

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts