Our great sponsors
-
external-secrets
External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
E.g. on a cloud provider use their secrets management solution. Bring the secrets from git/sops into their store, then for the application use external-secrets to bring a copy into your namespace and update your deployments with reloader.
-
Reloader
A Kubernetes controller to watch changes in ConfigMap and Secrets and do rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet and DeploymentConfig – [✩Star] if you're using it!
E.g. on a cloud provider use their secrets management solution. Bring the secrets from git/sops into their store, then for the application use external-secrets to bring a copy into your namespace and update your deployments with reloader.
-
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.
-
https://github.com/jkroepke/helm-secrets powered by sops
Related posts
- Learning with K3s at home. Is it "better" to store secrets encrypted in the git repo (e.g., sealed-secrets) or in a separately managed secret database (e.g., vault)?
- How to securely store configs across microservices and not commit secrets to vc
- Storing secrets in distributed binaries?
- Self-hosted Secrets Manager (or something alike)
- Surf CLI - Multiple AWS Accounts support! (Text search DynamoDB, S3 and more)