feat(rfcs): RFC 0014 self-service cache

[sduranc]

Problem

#3472 contains an RFC for a self-service cache built on Azure Managed Redis. The plan changed: we start with Valkey in the cluster.

Rendered Document

https://github.com/Altinn/altinn-platform/blob/feat/rfc-0014-self-service-cache/rfcs/0014-self-service-cache.md

Fix

This PR adds only the RFC, rewritten in Simplified Technical English:

• A team creates a Cache resource. The default engine is Valkey, in the cluster.
• dis-cache-operator delegates to the official valkey-operator (github.com/valkey-io/valkey-operator), the same way pgsql and vault delegate to ASO. The upstream operator is alpha; our own CRD protects teams from its API changes.
• The Azure Managed Redis design moved to Future possibilities: a later CRD option (for example type: managed) can create it through ASO. ASO v2.19.0 has the access-policy type this needs.
• Open questions are listed: access-control defaults, size-to-resource mapping, team capacity limits, and how the platform installs the upstream operator.

Rollout

Documentation only. The implementation follows in the PR sequence started with #3948 and #3949.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5ca0f429-fe2c-40d6-9497-c551aee63c4b

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}