radius-project / radius-project/roadmap
External data store for Radius
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Overview of roadmap item
Today, Radius stores its configuration and resource data in etc within the host Kubernetes cluster. This presents challenges for users backing up their Radius resource data and coordinating with Kubernetes cluster updates. This roadmap item is to implement options for advanced Radius deployments which use an external data store provided by the user. The first supported external data store should be PostgreSQL
Related issues
### Related issues
- [ ] https://github.com/radius-project/radius/issues/8096
- [ ] https://github.com/radius-project/radius/issues/7975
- [ ] https://github.com/radius-project/radius/issues/8071
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing related issues 8096, 7975, and 8071 to understand the planned scope for external data storage. Identify the deployment and data-storage entry points described there, then define the PostgreSQL-backed deployment options and acceptance criteria for advanced Radius installations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100