Regions
Regions in the Polycrate API: the generic platform service layer for location-bound infrastructure (storage, loadbalancing, controlplanes) and the soft migration away from S3Cluster and LoadbalancerRegion.
Regions
A Region is the generic platform service layer for location-bound infrastructure — storage, loadbalancing and controlplanes share the same abstraction model.
Historically, separate models existed (S3Cluster, LoadbalancerRegion). Region replaces
them step by step (soft migration, without a breaking change for existing buckets and
LBIs).
What a Region Represents
| Aspect | Meaning |
|---|---|
| Location / capacity | Link to workspace, cluster, reachability |
| Service offering | e.g. S3 API, HAProxy edge, controlplane IPAM |
| UI/API | CRUD, bootstrap and config tabs, reachability |
Region reconciliation checks, among other things, reachability (interval typically 300s). The detail UI contains bootstrap and config areas for commissioning.
Soft Migration
- Existing S3Bucket and LoadbalancerInstance objects remain usable.
- Internally they already run via Region or legacy bridges.
- Tables and admin may show a "Legacy Bridge" marker until the replacement is complete.
Further phases (S3/loadbalancer reconciliation entirely without legacy models) are planned on the product side; this document describes the current state of the soft migration.
Relationship to Other Objects
Region
├── workspace / organization / k8s_cluster (depending on service)
├── S3 / Object Storage (formerly S3Cluster)
├── Loadbalancer deployments (formerly LoadbalancerRegion)
└── IPAM Prefix (e.g. purpose=controlplane)
- LoadBalancer — deployments per region via Block Rollout
- S3 Buckets — region resolution on bucket create
- K8sControlplane — IPAM via prefix with region
- PoPs & Providers — geographic / provider assignment
Related Topics
- Block Rollout
- Endpoint Monitoring — including S3 API and edge reachability