You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add CI coverage for database.enabled=true install #12227
PR #12214 added database.enabled=true support (PostgreSQL-backed control plane for Repo Radius / rad startup / rad shutdown). During review, two blocking bugs in the database-enabled path (a non-existent mirror image tag → ImagePullBackOff, and missing per-RP GRANTs → permission denied for table resources) reached the PR because no CI job exercises database.enabled=true — the default functional suite installs with database.enabled=false.
PR #12214 added cheap regression guards via helm template assertions (image reference + GRANT statements), but those only validate rendering, not an actual install-and-run.
Acceptance criteria
A CI job installs Radius with database.enabled=true on a kind cluster and confirms the control plane reaches a healthy state (pods Ready, no ImagePullBackOff, no permission denied crash).
Ideally exercises a minimal deploy so the PostgreSQL store is actually written and read.
Runs on PRs that touch the Helm chart database templates and/or the database provider code.
The env-gated end-to-end lifecycle test at test/functional-portable/statestore (RADIUS_STATE_E2E) already exercises install→deploy→shutdown→startup with database.enabled=true; this issue may be satisfiable by wiring that test into CI once the cluster-create workflow lands.
A project maintainer will review this issue and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Activity
radius-triage commentedon Jun 24, 2026
👋 @sylvainsf Thanks for filing this issue.
A project maintainer will review this issue and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
radius-triage commentedon Jun 29, 2026
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
nicolejms commentedon Jun 29, 2026
bringing into next sprint. Sylvain has fix in his branch.
Add CI coverage for database.enabled=true install
Add CI coverage for database.enabled=true install (radius-project#12771)