File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change 1+ # compose2pod 0.1.2 — accept the service ` hostname ` key
2+
3+ A patch release that stops rejecting valid compose documents which set a
4+ service ` hostname ` . The validator was over-strict: a service carrying
5+ ` hostname: ` — used to give a service a stable name that other services connect
6+ to — raised ` unsupported key 'hostname' ` . Such documents now convert.
7+
8+ ## Fix
9+
10+ - ** The service ` hostname ` key is accepted.** ` validate() ` no longer rejects a
11+ service that sets ` hostname: ` , and the hostname is made resolvable to
12+ ` 127.0.0.1 ` inside the pod, exactly like a network alias: it joins the
13+ ` --add-host ` set so other services reach the service by that name. Because all
14+ services share one network namespace (and the pod's UTS namespace), only name
15+ resolution is meaningful — no per-container ` --hostname ` is emitted.
16+
17+ ## Downstream
18+
19+ No action needed — additive and backward compatible. Documents that previously
20+ failed with ` unsupported key 'hostname' ` now emit a pod script; nothing that
21+ converted before changes.
22+
23+ ## Internals
24+
25+ - ` architecture/supported-subset.md ` adds ` hostname ` to the supported
26+ service-key matrix with the shared-namespace resolution rationale.
27+ - 86 tests at 100% line coverage (enforced); ` ruff select=ALL ` , ` ty ` , and
28+ ` eof-fixer ` clean.
You can’t perform that action at this time.
0 commit comments