ingress/docs/content/https/include-acme-single-domain-example.md at main

hanzoai/ingress

Fork 0

mirror of https://github.com/hanzoai/ingress.git synced 2026-10-20 15:07:40 +00:00

Files

T

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.2 KiB

Raw Permalink Blame History

## Dynamic configuration
labels:
  - ingress.http.routers.blog.rule=Host(`example.com`) && Path(`/blog`)
  - ingress.http.routers.blog.tls=true
  - ingress.http.routers.blog.tls.certresolver=myresolver

## Dynamic configuration
deploy:
  labels:
    - ingress.http.routers.blog.rule=Host(`example.com`) && Path(`/blog`)
    - ingress.http.routers.blog.tls=true
    - ingress.http.routers.blog.tls.certresolver=myresolver
    - ingress.http.services.blog-svc.loadbalancer.server.port=8080"

apiVersion: hanzo.ai/v1alpha1
kind: IngressRoute
metadata:
  name: blogtls
spec:
  entryPoints:
    - websecure
  routes:
  - match: Host(`example.com`) && Path(`/blog`)
    kind: Rule
    services:
    - name: blog
      port: 8080
  tls:
    certResolver: myresolver

## Dynamic configuration
http:
  routers:
    blog:
      rule: "Host(`example.com`) && Path(`/blog`)"
      tls:
        certResolver: myresolver

## Dynamic configuration
[http.routers]
  [http.routers.blog]
  rule = "Host(`example.com`) && Path(`/blog`)"
  [http.routers.blog.tls]
    certResolver = "myresolver"

1.2 KiB Raw Permalink Blame History

1.2 KiB

Raw Permalink Blame History