Files
zeekayandHanzo Dev 15d100931d
Hanzo CI/CD / cicd (push) Failing after 9m46s
CI/CD / cicd (push) Failing after 10m4s
Name the ingress in the docs, and fix what that exposed
Most of it was stale, not cosmetic: the docs taught `TRAEFIK_*` env,
`traefik.http.*` labels, `traefik.ingress.kubernetes.io/` annotations,
`.traefik.yml` plugins and `traefik_*` metrics. This binary answers to
`INGRESS_*`, `ingress.http.*`, `ingress.kubernetes.io/`, `.ingress.yml` and
`ingress.*` — a reader following the old text configured nothing.

Two were worse than stale. Gateway API examples gave `group: traefik.io` for an
IngressService backendRef, which kubernetes.go:1265 refuses against hanzo.ai.
The contributing guide built with `github.com/traefik/ingress` ldflags against
a module that is `github.com/hanzoai/ingress/v3`.

script/code-gen.sh globs `hanzo.ai_*.yaml` and matched nothing — the per-CRD
dumps had been deleted and never regenerated, so `cat` failed the script under
`set -e`. controller-gen v0.19.0 restores all ten; they concatenate
byte-for-byte into the committed definition and fixture.

CHANGELOG.md is untouched: 6,789 lines of imported release history, where a
rewrite would falsify the record rather than rebrand it. `@traefiklabs/faency`,
`traefik/whoami`, k3s's `--disable=traefik`, the `traefik.io` CRD group and the
MIT attribution stay — upstream's addresses, not our brand.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 13:01:19 -07:00

1.7 KiB

title, description
title description
Hanzo Ingress Plugins Documentation Learn how to use Hanzo Ingress Plugins. Read the technical documentation.

Hanzo Ingress Plugins and the Plugin Catalog

Plugins are a powerful feature for extending Hanzo Ingress with custom features and behaviors. The Plugin Catalog is a software-as-a-service (SaaS) platform that provides an exhaustive list of the existing plugins.

??? note "Plugin Catalog Access" You can reach the Plugin Catalog from the Hanzo Ingress Dashboard using the Plugins menu entry.

To add a new plugin to a Hanzo Ingress instance, you must change that instance's static configuration. Each plugin's Install section provides a static configuration example. Many plugins have their own section in the Hanzo Ingress dynamic configuration.

To learn more about Hanzo Ingress plugins, consult the documentation.

!!! danger "Experimental Features" Plugins can change the behavior of Hanzo Ingress in unforeseen ways. Exercise caution when adding new plugins to production Hanzo Ingress instances.

Build Your Own Plugins

Hanzo Ingress users can create their own plugins and share them with the community using the Plugin Catalog.

Hanzo Ingress will load plugins dynamically. They need not be compiled, and no complex toolchain is necessary to build them. The experience of implementing a Hanzo Ingress plugin is comparable to writing a web browser extension.

To learn more about Hanzo Ingress plugin creation, please refer to the developer documentation.

{% include-markdown "includes/ingress-for-business-applications.md" %}