What is the problem?
Teams have no self-service cache in DIS (parent: #3944).
What we do
RFC 0014 (#3952) describes the plan:
- A team creates a
Cache resource in its namespace and gets a Valkey instance in the cluster.
dis-cache-operator does not run Valkey itself. It delegates to the official valkey-operator, the same way pgsql and vault delegate to ASO.- Access control: NetworkPolicy (same namespace only), a password in a Secret, and TLS through cert-manager.
- One cache per application. No shared Valkey cluster across teams.
- Managed Redis in Azure can become an option in the same CRD later.
This answers the open questions in #3944: Valkey first, persistence off by default, managed Redis as a later option for teams that need it.
Status
| Step |
PR |
| RFC 0014 |
#3952 |
| Shared identity package |
#3948 |
Operator scaffold (Cache CRD) |
#3949 |
The RFC needs review and acceptance. The old Azure Redis PR (#3472) will be closed.
🤖 Generated with Claude Code
What is the problem?
Teams have no self-service cache in DIS (parent: #3944).
What we do
RFC 0014 (#3952) describes the plan:
Cacheresource in its namespace and gets a Valkey instance in the cluster.dis-cache-operatordoes not run Valkey itself. It delegates to the official valkey-operator, the same way pgsql and vault delegate to ASO.This answers the open questions in #3944: Valkey first, persistence off by default, managed Redis as a later option for teams that need it.
Status
CacheCRD)The RFC needs review and acceptance. The old Azure Redis PR (#3472) will be closed.
🤖 Generated with Claude Code