# mvirt 0.29.6

migrations: no
wire: unchanged
rev: b0ac157dd127a0e76bfe1b38410774c9e1731700

mvirt 0.29.6

Ingress survives a host loss better, lifecycle and deploy events reach the
project feed, CSP findings are replicated, and cold logs across midnight are
found again.

- cplane: PaaS ingress fleets run two Envoy replicas by default, spread across
  hosts; platform-default fleets still at 1 are raised once (refs #414).
- cplane, console: lifecycle events carry their project; an app deploy emits
  `deploy` events (started / replica-ready / succeeded|failed); the log
  histogram shows them as needles (refs #30).
- cplane: CSP report findings are replicated `event` rows with warn severity,
  relayed from followers to the leader (refs #193 #413) — the #413 watch
  window starts with this release.
- logs: the spooler splits segments at UTC midnight and reads also list the
  following day, so midnight-spanning segments are found.
- console: /platform/setup is the manifest export page; the file-managed
  inspect mode is gone (closes #223).

Not included: #415 (fence disk-less pods on an Offline host) is held for a
design decision.


## Upgrading

Point your flake's `mvirt` input at this release and redeploy the control-plane
host first, then each node in turn:

```
nix run .#colmena -- apply boot --reboot --on <control-plane host>
nix run .#colmena -- apply boot --reboot --on <node>   # one at a time
```

This release adds no migrations, so the control-plane host rolls back the same way
a node does: boot the previous NixOS generation.