zededa:patch-envelopes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| zededa:patch-envelopes [2026/07/23 23:15] – mc | zededa:patch-envelopes [2026/07/23 23:24] (current) – mc | ||
|---|---|---|---|
| Line 92: | Line 92: | ||
| > instance (the same '' | > instance (the same '' | ||
| > An app on a pure switch NI with no local-NI path will not see it. | > An app on a pure switch NI with no local-NI path will not see it. | ||
| + | |||
| + | ==== ⚠ Gotcha — reachability of 169.254.169.254 ==== | ||
| + | |||
| + | The metadata service **lives inside EVE** on the edge node — it is **not** exposed outside the | ||
| + | node. This has direct consequences for how the workload is networked: | ||
| + | |||
| + | * **Local-type NI can reach it; Switch-type cannot.** A **Local** network instance routes to '' | ||
| + | * **Multi-NIC default-route trap.** If a workload is attached to **two** network instances (e.g. one Local + one Switch, or two with default routes) and **both provide a default gateway**, the guest may pick the **Switch** interface as its default route — and then traffic to '' | ||
| + | * **Fix — configure it on the Local network instance, NOT inside the guest.** EVE hands routes to the app through the **Local NI configuration** (advertised to the attached app via the NI's DHCP), not via manual '' | ||
| + | prefix | ||
| + | gateway = "< | ||
| + | }</ | ||
| **How to detect changes without busy-polling: | **How to detect changes without busy-polling: | ||
zededa/patch-envelopes.1784848506.txt.gz · Last modified: by mc
