Skip to content

Standardize runtime container names - #49

Merged
vishr merged 1 commit into
mainfrom
feat/runtime-container-names
Aug 16, 2026
Merged

vishr merged 1 commit into
mainfrom
feat/runtime-container-names

Conversation

@vishr

@vishr vishr commented Aug 16, 2026

Copy link
Copy Markdown
Member

Summary

  • name stable application containers as app-component-replica, including singleton replica 1
  • rename the managed host proxy to onebox-proxy
  • keep persistent/provider names collision-safe and document the runtime grammar
  • add collision-property coverage and live Docker name assertions

Breaking change

No legacy aliases or compatibility naming are included. Existing workloads converge through normal label-based rolling; supporting services retain their persistent volumes. An existing managed proxy must be removed before the first deployment with this version because the old proxy still owns ports 80/443.

Verification

  • just check
  • Docker-gated zero-downtime E2E: v1, rolling v2, unchanged v2; exact obe2e-web-1 name; zero failed requests
  • git diff --check
  • typos on changed source and documentation

Use <app>-<component>-<replica> for stable application containers and onebox-proxy for the host proxy.

BREAKING CHANGE: runtime container and managed proxy names change without legacy aliases or compatibility naming.
@vishr
vishr merged commit 1729b0c into main Aug 16, 2026
5 checks passed
@vishr
vishr deleted the feat/runtime-container-names branch August 16, 2026 23:19
vishr added a commit that referenced this pull request Aug 18, 2026
vishr added a commit that referenced this pull request Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant