Ingress

The hanzo ingress commands.

Also for this capability: API · CLI · MCP · SDKs

Your edge: automatic TLS certificates and hostname routing to any backend, changed live.

API reference →

hanzo ingress routes list

Every command takes --json for the raw response and --help for its own flags. Sign in once with hanzo auth login; the commands below use that session, and the org they act in is the one it carries.

CommandWhat it does
hanzo ingress statusReports the ingress edge's live posture: the role this instance runs in (app or edge), whether its listeners are bound and on which addresses, the ACME posture (staging flag and certificate cache directory), how many hosts the compiled route table currently serves, and how many the ACME HostPolicy will issue a certificate for.

Middlewares

CommandWhat it does
hanzo ingress middlewares createCreates or replaces one edge transform and hot-applies it.
hanzo ingress middlewares get <id>Returns one of the caller org's edge transforms by id.
hanzo ingress middlewares listReturns every edge transform the caller's org has configured, ordered by id.
hanzo ingress middlewares rm <id>Removes one of the caller org's edge transforms and hot-applies the change.
hanzo ingress middlewares set <id>Creates or replaces one edge transform and hot-applies it.

Routes

CommandWhat it does
hanzo ingress routes createCreates or replaces one routing rule and hot-applies the new table — there is no config file and no restart.
hanzo ingress routes get <id>Returns one of the caller org's routing rules by id.
hanzo ingress routes listReturns every routing rule the caller's org has configured, ordered by id.
hanzo ingress routes rm <id>Removes one of the caller org's routing rules and hot-applies the shrunken table, freeing its host for another claim.
hanzo ingress routes set <id>Creates or replaces one routing rule and hot-applies the new table — there is no config file and no restart.

Services

CommandWhat it does
hanzo ingress services createCreates or replaces one backend pool and hot-applies it.
hanzo ingress services get <id>Returns one of the caller org's backend pools by id.
hanzo ingress services listReturns every backend pool the caller's org has configured, ordered by id.
hanzo ingress services rm <id>Removes one of the caller org's backend pools and hot-applies the change.
hanzo ingress services set <id>Creates or replaces one backend pool and hot-applies it.

TLS

CommandWhat it does
hanzo ingress tls getReturns the caller org's ACME intent together with the edge-wide TLS facts it lands in: which role this instance runs in, whether its listeners are bound, every host the ACME HostPolicy will issue a certificate for (the union across ALL orgs of TLS-marked routes and configured extraHosts, because one process holds one certificate cache), and the ACME directory and account email the process was started with.
hanzo ingress tls replaceReplaces the caller org's ACME intent and hot-applies what can be hot-applied.
Was this page useful?