Перейти к содержимому

Tunnel lifecycle

Окно терминала
hubctl tunnel list
hubctl test tunnel corp-private

A successful preflight probe is evidence for the tunnel, not a bypass for deployment review.

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/16
hubctl tunnel zones corp-private --add corp.example
hubctl validate
hubctl deploy --confirm-within 5m
hubctl confirm

Withdraw the exact route or zone with --remove, then deploy the revised plan.

Disable a tunnel only after confirming that affected devices have an intentional alternative.

Окно терминала
hubctl tunnel disable corp-private
hubctl deploy --confirm-within 5m
hubctl confirm

After repair, enable it, run the probe again, and deploy. Run hubctl rollback immediately if the new revision harms connectivity.