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.9 KiB
1.9 KiB
title, description
| title | description |
|---|---|
| Hanzo Ingress GrpcWeb Documentation | In Hanzo Ingress's HTTP middleware, GrpcWeb converts a gRPC Web requests to HTTP/2 gRPC requests. Read the technical documentation. |
The grpcWeb middleware converts gRPC Web requests to HTTP/2 gRPC requests before forwarding them to the backends.
!!! tip
Please note, that Hanzo Ingress needs to communicate using gRPC with the backends (h2c or HTTP/2 over TLS).
Check out [Exposing gRPC Services](../../../../expose/overview.md#exposing-grpc-services) for more details.
Configuration Examples
http:
middlewares:
test-grpcweb:
grpcWeb:
allowOrigins:
- "*"
[http.middlewares]
[http.middlewares.test-grpcweb.grpcWeb]
allowOrigins = ["*"]
labels:
- "ingress.http.middlewares.test-grpcweb.grpcweb.allowOrigins=*"
{
//...
"Tags" : [
"ingress.http.middlewares.test-grpcweb.grpcWeb.allowOrigins=*"
]
}
apiVersion: hanzo.ai/v1alpha1
kind: Middleware
metadata:
name: test-grpcweb
spec:
grpcWeb:
allowOrigins:
- "*"
Configuration Options
| Field | Description | Default | Required |
|---|---|---|---|
allowOrigins |
List of allowed origins. A wildcard origin * can also be configured to match all requests.More information here. |
[] | No |
allowOrigins
More information including how to use the settings can be found at: