·
5 commits
to main
since this release
Changes in valkey
From PR: #139 (Issues closed: #136 #137)
- Complete removal of Kubernetes Reflector and Random Provider since its
all being managed using OpenBao and External Secrets Operator - READMEs updated to denote the removal of the components
- Deployment tested to make sure there are no errors and Random Provider
doesn't creep in
From PR: #130 (Issues closed: #120)
- Shifted secrets management for Valkey Credentials to External Secrets
Operator - No dependent module however have setup outputs for other modules to
use - For generating passwords, using External Secrets Operator for the same
From PR: #100 (Issues closed: #99)
- Setup monitoring dashboards for Valkey in an automated fashion
completed - Implemented Deployment of Redis Exporter to expose metrics for the
Valkey Cluster - Allowed network calls to happen to the Valkey Cluster
From PR: #60 (Issues closed: #59)
- Moved example setup to this repository
From PR: #43 (Issues closed: N/A)
- Setup Pod Affinity along with Topology Spread for Valkey Pods (#40)
- Setup Pod Disruption Budget to keep 2 Valkey Pods running (#41)
- Setup Network Policies to restrict network access to Valkey (#42)
From PR: #34 (Issues closed: #33)
- Used native Kubernetes Objects for deploying Valkey instead of using
Bitnami Helm Charts - Preserved features that were being used such as TLS connections
- Deployed a service exposing only the primary pod for usage