Bundle the web server as... helm chart maybe? #119

New issue

Closed

opened 2026-07-20 19:17:02 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-07-20 19:17:02 +00:00

Owner

No description provided.

coilyco-ops referenced this issue

2026-07-25 13:36:45 +00:00

[interactive] Resolve remaining Eco App decisions and live checkpoints #155

coilyco-ops added the

autonomy

async-consult

label

2026-07-25 15:00:17 +00:00

coilyco-ops commented

2026-07-26 00:10:48 +00:00

Member

Decision: keep eco-app on the established image plus deploy-manifest model. Do not add a Helm chart.

The repo already ships the portable unit, one fused OCI image with environment-driven configuration. The installation-specific namespace, ingress, ExternalSecrets, sidecars, and rollout logic correctly live one layer higher in coilyco-bridge/deploy/services/eco-app. A chart here would duplicate deployment config across layers and create a distribution surface with no current consumer.

This matches the repo boundary in AGENTS.md and the deployment-of-one posture. A Helm chart becomes justified only if eco-app gains multiple independent installers that need a supported values contract. That should be a new issue with those consumers and acceptance criteria, not speculative packaging here.

Closing with the current manifest pattern selected.

Decision: keep eco-app on the established image plus deploy-manifest model. Do not add a Helm chart. The repo already ships the portable unit, one fused OCI image with environment-driven configuration. The installation-specific namespace, ingress, ExternalSecrets, sidecars, and rollout logic correctly live one layer higher in `coilyco-bridge/deploy/services/eco-app`. A chart here would duplicate deployment config across layers and create a distribution surface with no current consumer. This matches the repo boundary in AGENTS.md and the deployment-of-one posture. A Helm chart becomes justified only if eco-app gains multiple independent installers that need a supported values contract. That should be a new issue with those consumers and acceptance criteria, not speculative packaging here. Closing with the current manifest pattern selected.

coilyco-ops closed this issue

2026-07-26 00:10:49 +00:00

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-gaming/eco-app#119

No description provided.

Rows
Columns