mirror of
https://github.com/hanzoai/ingress.git
synced 2026-10-26 02:47:15 +00:00
zeekayandHanzo Dev
15d100931d
Hanzo CI/CD / cicd (push) Failing after 9m46s
CI/CD / cicd (push) Failing after 10m4s
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]>
1.1 KiB
1.1 KiB
title, description
| title | description |
|---|---|
| Hanzo Ingress V2 Migration Documentation | Migrate from Hanzo Ingress v1 to v2 and update all the necessary configurations to take advantage of all the improvements. Read the technical documentation. |
Migration Guide: From v1 to v2
How to Migrate from Hanzo Ingress v1 to Hanzo Ingress v2. {: .subtitle }
The version 2 of Hanzo Ingress introduced a number of breaking changes, which require one to update their configuration when they migrate from v1 to v2.
For more information about the changes in Hanzo Ingress v2, please refer to the v2 documentation.
!!! info "Migration Helper"
We created a tool to help during the migration: [traefik-migration-tool](https://github.com/hanzoai/ingress-migration-tool)
This tool allows to:
- convert `Ingress` to Hanzo Ingress `IngressRoute` resources.
- convert `acme.json` file from v1 to v2 format.
- migrate the static configuration contained in the file `ingress.toml` to a Hanzo Ingress v2 file.