v0.7.0

[0.7.0] - 2026-10-31

Upgrade notes / operator action required

• Controller --pod-cidr is now repeatable, at most one per family. On a
  dual-stack cluster pass it once per family, e.g.
  --pod-cidr=10.42.0.0/16 --pod-cidr=fd00:42::/56; without the v6 CIDR,
  non-hostNetwork v6 pod backends are rejected. Two CIDRs of the same family
  are a startup error. A single-stack cluster keeps its one flag unchanged.

• Ingress is withheld until the startup LISTs complete. The controller
  publishes no status.loadBalancer.ingress until its first Service,
  EndpointSlice and Node LISTs have all completed (previously it published
  --node-ip's family alone from the first Service event). The stock
  DaemonSet now has an exec readinessProbe that checks the --ready-file
  path (/tmp/beep-ready), created at that point; pods report NotReady during
  startup. Custom manifests must add the probe and pass --ready-file. See
  deploy/README.md, "Startup readiness".

Added

• deploy/README.md documents uninstalling beep, including the node-level
  residue it leaves behind.

Changed

• Updated to aya 0.16, with the loader and controller adapted to its API.
• Updated politeia to v0.3.2.
• Dependency and CI-action bumps (Renovate).

Fixed

• The "shares no address family" peer WARN no longer fires when this node has
  any address in a family the peer has (e.g. a dual-stack node with a v4
  --node-ip and a v6-only peer, which tunnels fine over v6).
• A Service that left type=LoadBalancer while the controller was down now has
  both of this node's ingress entries withdrawn; the clear is deferred until
  the initial LISTs complete instead of covering --node-ip's family alone.