Tunnel lifecycle
Probe first
Section titled “Probe first”hubctl tunnel listhubctl test tunnel corp-privateA successful preflight probe is evidence for the tunnel, not a bypass for deployment review.
Manage private destinations
Section titled “Manage private destinations”Routes are IP subnets and zones are private DNS suffixes. Both are desired-state changes: validate and deploy them.
hubctl tunnel routes corp-private --add 10.20.0.0/16hubctl tunnel zones corp-private --add corp.examplehubctl validatehubctl deploy --confirm-within 5mhubctl confirmWithdraw the exact route or zone with --remove, then deploy the revised plan.
Maintenance and recovery
Section titled “Maintenance and recovery”Disable a tunnel only after confirming that affected devices have an intentional alternative.
hubctl tunnel disable corp-privatehubctl deploy --confirm-within 5mhubctl confirmAfter repair, enable it, run the probe again, and deploy. Run hubctl rollback immediately if the new revision harms connectivity.