How equinor/radix-platform works
Radix is Equinor’s Platform-as-a-Service, but this repository is an umbrella and infrastructure repository rather than the implementation of its developer-facing runtime. The documented user path is application registration through the Web Console, followed by Radix’s testing, build, deployment, runtime, and monitoring capabilities; those services live in other repositories. This tree contains Terraform infrastructure definitions and operational scripts, including cluster setup and monitoring and backup recovery. No source excerpts were available, so links between those infrastructure components are omitted where their callers or data flow cannot be verified.
Main entry points: subscriptions Terraform deployments · modules Cloud resource modules · s940 Subscription configurations
Components 13
Developer workflow
- Application developer
- Radix Web Console
- Radix platform
Cloud infrastructure
- Terraform deployments
terraform/subscriptions - Cloud resource modules
terraform/subscriptions/modules - Subscription configurations
terraform/subscriptions/s940
Platform operations
- AKS cluster setup
scripts/aks - Flux operations
scripts/flux - Prometheus recovery
scripts/prometheus-operator - Application restore
scripts/velero/restore - Identity credentials
scripts/service-principals-and-aad-apps - Certificate issuers
scripts/cert-manager
Other components
- Azure
Connections 6
- Application developer → Radix Web Console: registers application
- Radix Web Console → Radix platform: registers application
- Radix platform → Application developer: provides platform services
- Terraform deployments → Cloud resource modules: uses modules
- Terraform deployments → Subscription configurations: defines deployments
- Terraform deployments → Azure: provisions resources