v0.x-to-binary-shared

To consolidate multi-service Docker image builds in a Forge project, opt into binary: shared in your forge.yaml file and run forge generate to rewrite the shared-binary entrypoints and deploy manifests. This reduces CI image build and push time by producing one shared image.

A MultiServiceApplication KCL deploy shape replaces per-service Application blocks by referencing one shared Docker image while preserving per-service Deployment, Service, and RBAC scope. You need it when migrating to a shared binary model with 3 or more services.

Yes, you can use cobra subcommands to boot a specific service from a shared Go binary. The migration updates BootstrapOnly behavior so starting with a specific subcommand constructs only that service’s dependency graph, optimizing runtime boot.

Migrating to a shared binary model works well for Forge projects with 3 or more services, shared internal libraries, and deploy manifests containing many near-identical Application blocks where CI image build dominates cycle time. Validate that one distinct Docker image is produced.

Switching a Forge project to a shared binary deployment requires explicit opt-in via forge.yaml and regeneration with forge generate. You must validate that exactly one distinct Docker image is referenced and N deployments are produced to ensure operational consistency.