ingress/docs/content/operations/include-api-examples.md at main

hanzoai/ingress

Fork 0

mirror of https://github.com/hanzoai/ingress.git synced 2026-10-26 02:47:15 +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

2.3 KiB

Raw Permalink Blame History

# Dynamic Configuration
labels:
  - "ingress.http.routers.api.rule=Host(`ingress.example.com`)"
  - "ingress.http.routers.api.service=api@internal"
  - "ingress.http.routers.api.middlewares=auth"
  - "ingress.http.middlewares.auth.basicauth.users=test:$$apr1$$H6uskkkW$$IgXLP6ewTrSuBkTrqE8wj/,test2:$$apr1$$d9hr9HBB$$4HxwgUir3HP4EsggP/QNo0"

# Dynamic Configuration
deploy:
  labels:
    - "ingress.http.routers.api.rule=Host(`ingress.example.com`)"
    - "ingress.http.routers.api.service=api@internal"
    - "ingress.http.routers.api.middlewares=auth"
    - "ingress.http.middlewares.auth.basicauth.users=test:$$apr1$$H6uskkkW$$IgXLP6ewTrSuBkTrqE8wj/,test2:$$apr1$$d9hr9HBB$$4HxwgUir3HP4EsggP/QNo0"
    # Dummy service for Swarm port detection. The port can be any valid integer value.
    - "ingress.http.services.dummy-svc.loadbalancer.server.port=9999"

apiVersion: hanzo.ai/v1alpha1
kind: IngressRoute
metadata:
  name: ingress-dashboard
spec:
  routes:
  - match: Host(`ingress.example.com`)
    kind: Rule
    services:
    - name: api@internal
      kind: IngressService
    middlewares:
      - name: auth
---
apiVersion: hanzo.ai/v1alpha1
kind: Middleware
metadata:
  name: auth
spec:
  basicAuth:
    secret: secretName # Kubernetes secret named "secretName"

# Dynamic Configuration
- "ingress.http.routers.api.rule=Host(`ingress.example.com`)"
- "ingress.http.routers.api.service=api@internal"
- "ingress.http.routers.api.middlewares=auth"
- "ingress.http.middlewares.auth.basicauth.users=test:$$apr1$$H6uskkkW$$IgXLP6ewTrSuBkTrqE8wj/,test2:$$apr1$$d9hr9HBB$$4HxwgUir3HP4EsggP/QNo0"

# Dynamic Configuration
http:
  routers:
    api:
      rule: Host(`ingress.example.com`)
      service: api@internal
      middlewares:
        - auth
  middlewares:
    auth:
      basicAuth:
        users:
          - "test:$apr1$H6uskkkW$IgXLP6ewTrSuBkTrqE8wj/"
          - "test2:$apr1$d9hr9HBB$4HxwgUir3HP4EsggP/QNo0"

# Dynamic Configuration
[http.routers.my-api]
  rule = "Host(`ingress.example.com`)"
  service = "api@internal"
  middlewares = ["auth"]

[http.middlewares.auth.basicAuth]
  users = [
    "test:$apr1$H6uskkkW$IgXLP6ewTrSuBkTrqE8wj/",
    "test2:$apr1$d9hr9HBB$4HxwgUir3HP4EsggP/QNo0",
  ]

2.3 KiB Raw Permalink Blame History

2.3 KiB

Raw Permalink Blame History