Cette page a été traduite automatiquement. Lire l’original en anglais.

Component

core/gateway/higress

Higress, an open-source gateway built on Envoy and configured through Kubernetes resources: its routes are ingresses, the services it reaches are its own registry's entries, and its controls are WebAssembly plugins on the routes they act on. It terminates client HTTP on its proxy port, publishing its host, port and protocol. It serves models: each model wired to its models socket is reached under an alias at /<alias>/v1 through Higress's AI proxy, sent to the endpoint and model name the model publishes, presenting the connection's credential from its Secret; over https it checks that the model's certificate chains to the system's trust anchors and names its host. Connections naming one alias in serves share its requests. It publishes the route of values.model as its endpoint and that alias as its model, so an agent's model socket takes it in place of a model; with nothing wired both are empty. On those routes it masks requests, keeps a token budget in its cache socket's store, records each model request in its access log and sets each route's retry, refusing by name what Higress cannot keep; it declares no callers. Reply validation, the fallback chain, the semantic cache, the prompt-injection shield and latency-based target selection halt the build naming what Higress lacks. It pulls its plugin modules from Higress's plugin registry at run time, which the cluster must reach and the build cannot check. It is realized on Kubernetes by `higress-chart` alone, and publishes the pod label, port name and path a scraper discovers its gateway's metrics by.

Provenance

OfficielSigné par une identité de signature que ce catalogue reconnaît comme éditeur officiel.
Empreinte du contenu
sha256:8b92c8a380a01667259d0b041b43a42dc1c93b50b58b21741d1cc4a57a8260f9
Publié
2026-11-10T10:11:55Z
Identité de signature
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officielapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:ef9dfa3941c48639070a7b9379a7ff22eb5637b82b98304936be0d1c243fd7b7

Référence à cette version

oci://hub.aggrega.ai/component/core/gateway/higress:1.0.0

Paramètres du développeur

Valeurs que le développeur définit dans l’Aggregate.

NomTypeValeur par défautObligatoireDescription
modelstring—nonThe alias this gateway publishes as its model, and whose route its published endpoint addresses — a serves value a models connection names, or the name of a connection naming none. It must be an alias the models socket serves, and the build halts naming this value otherwise; it is required while the models socket holds a connection, and omitted while it holds none.

Dimensionnement de l’opérateur

Dimensionnement de l’infrastructure que l’opérateur ajuste pour chaque environnement.

NomTypeValeur par défautObligatoireDescription
http_portinteger (min 1, max 65535)80nonProxy data-plane port consumers connect to.
source_versionstring—nonVersion of the Higress chart the chart-backed realization pulls. The realization holds the chart versions its configuration is proven at, and the build halts naming them on any other.
computeobject—non—
overridesobject (open)—nonProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Contrat de sortie

Valeurs que ce composant publie vers les consommateurs via la topologie uses.

NomTypeValeur par défautObligatoireDescription
hoststring—ouiIn-cluster DNS name of the Service fronting the gateway's proxy, the name alone without a namespace. A consumer sends its client traffic here rather than to the service behind the gateway.
portinteger—ouiTCP port that Service accepts proxied traffic on, infra.http_port.
protocolstring—nonHow the published address is spoken to — `http`, so a consumer composes an address on that scheme.
endpointstring—nonFull base URL of the OpenAI-compatible API the gateway serves for the alias values.model names, with the host, the port and that alias's route already composed. A caller hands it to a client library as its base URL. Every other alias is served at the same host and port under its own name in the path. Empty while nothing is wired to the models socket.
modelstring—nonThe alias a consumer wired to the gateway sends as its model name: values.model. The route behind the endpoint asks each model for the name that model publishes, whatever name a request carries. Empty while nothing is wired to the models socket.
metrics_pod_selectorstring—nonKubernetes label selector matching the gateway's pods, for a scraper that discovers those pods directly rather than scraping one address. Published beside `metrics_pod_port` and `metrics_path`.
metrics_pod_portstring—nonName of the container port on those pods that carries the metrics, `istio-prom`.
metrics_pathstring—nonPath the metrics are served at on that port, `/stats/prometheus`.

Sockets uses

Les sockets de dépendance par lesquels ce composant se connecte. La cible de chaque connexion câblée via un socket doit satisfaire son sélecteur d’étiquettes, et chaque connexion peut porter une attache dans les emplacements que le socket déclare. Un emplacement obligatoire doit être rempli par chaque connexion que l’Aggregate ou la Release câble via le socket.

models

Sélecteur
component.aggrega.ai/category=ai-model
Injection
—

Emplacements que chaque connexion passant par ce socket peut remplir

EmplacementSélecteurObligatoireInjectionSensibleDescription
credentialfeature.aggrega.ai/kind=secretnon—ouiOptional credential the gateway presents to the model this connection reaches, as a bearer token. When attached, the AI proxy's configuration names the Secret the credential publishes and the data key holding the key there, and the Higress controller reads the key from that Secret, in the gateway's namespace, so the key appears in no rendered file. The credential must publish both, and a Secret name holding a dot halts the build, because Higress reads the name up to its first dot; a realization naming its own Secret after the connection and this slot writes such a dot, so realize it with one naming an existing Secret whose name holds none. Unattached, the gateway adds no credential.

cache

Sélecteur
datastore.aggrega.ai/engine=kv
Injection
—

Emplacements que chaque connexion passant par ce socket peut remplir

EmplacementSélecteurObligatoireInjectionSensibleDescription
credentialfeature.aggrega.ai/kind=secretnon—ouiOptional password the gateway's token budget presents to the Redis-protocol store this connection reaches. When attached, the budget's configuration names the Secret the credential publishes and the data key holding the password there, and the Higress controller reads the password from that Secret, in the gateway's namespace, so it appears in no rendered file. The credential must publish both, and a Secret name holding a dot halts the build, because Higress reads the name up to its first dot; realize it with one naming an existing Secret whose name holds none. Unattached, the plugin connects with no password, which is what the shipped store components expect by default.

Emplacements d’attache

Points de liaison nommés auxquels une Feature s’attache à ce composant. Le sélecteur d’un emplacement restreint la Feature qui peut le remplir, et sa liste inject indique comment le matériel de la Feature peut être livré. Un emplacement obligatoire doit être lié sur chaque instance, par une attache sur l’instance ou à une portée supérieure, et un emplacement sensible est déclaré pour traiter du matériel secret. Une Feature peut aussi s’attacher sous un nom qu’aucun emplacement ne déclare.

Aucun emplacement d’attache déclaré.

Liste d’autorisation d’auto-injection

Aucun canal d’auto-injection déclaré.

Relations

Arêtes typées vers et depuis d’autres entités publiées. Une référence sans cible publiée s’affiche comme une arête rompue plutôt que comme un lien.

Utilise

Utilisé par

Référence du concept Component →

Le catalogue Aggrega — un index ouvert de composants, de fonctionnalités, de recettes et des plugins qui en assurent le rendu.

Conçu avec le système de design partagé d’Aggrega.

Confidentialité