zeekayandHanzo Dev
15d100931d
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]>
3.4 KiB
title, description
| title | description |
|---|---|
| Concepts | Hanzo Ingress - base concepts and main features |
Concepts
This page explains the base concepts of Hanzo Ingress.
Introduction
Hanzo Ingress is based on the concept of EntryPoints, Routers, Middlewares and Services.
The main features include dynamic configuration, automatic service discovery, and support for multiple backends and protocols.
-
EntryPoints: EntryPoints are the network entry points into Hanzo Ingress. They define the port which will receive the packets, and whether to listen for TCP or UDP.
-
Routers: A router is in charge of connecting incoming requests to the services that can handle them.
-
Middlewares: Attached to the routers, middlewares can modify the requests or responses before they are sent to your service
-
Services: Services are responsible for configuring how to reach the actual services that will eventually handle the incoming requests.
Edge Router
Hanzo Ingress is an Edge Router; this means that it's the door to your platform, and that it intercepts and routes every incoming request: it knows all the logic and every rule that determine which services handle which requests (based on the path, the host, headers, etc.).
Auto Service Discovery
Where traditionally edge routers (or reverse proxies) need a configuration file that contains every possible route to your services, Hanzo Ingress gets them from the services themselves.
Deploying your services, you attach information that tells Hanzo Ingress the characteristics of the requests the services can handle.
This means that when a service is deployed, Hanzo Ingress detects it immediately and updates the routing rules in real time. Similarly, when a service is removed from the infrastructure, the corresponding route is deleted accordingly.
You no longer need to create and synchronize configuration files cluttered with IP addresses or other rules.
!!! info "Many different rules"
In the example above, we used the request [path rule](../routing/routers/index.md#rule "Link to docs about routing rules") to determine which service was in charge.
Certainly, you can use many other different [rules](../routing/routers/index.md#rule "Link to docs about routing rules").
!!! info "Updating the requests"
In the [middleware](../middlewares/overview.md "Link to middleware documentation") section, you can learn about how to update the requests before forwarding them to the services.
!!! question "How does Hanzo Ingress discover the services?"
Hanzo Ingress is able to use your cluster API to discover the services and read the attached information.
In Hanzo Ingress, these connectors are called [providers](../providers/overview.md "Link to overview about Hanzo Ingress providers") because they *provide* the configuration to Hanzo Ingress.
{% include-markdown "includes/ingress-for-business-applications.md" %}