Esta página se tradujo automáticamente. Leer el original en inglés.

Recipe

nemo-guardrails

The NeMo Guardrails server as a guard in a model's path, on Kubernetes via the helm provider's Workload synthesis, running the image in infra.image directly: a stateless Deployment, a ClusterIP Service on the port the guard answers on, and a ConfigMap carrying the guard's configuration as the product's own two files. Synthesized rather than wrapping a chart because the project publishes none. The ConfigMap's config.yaml names the Hugging Face classifier rail on the guard's input, pointed at the endpoint and model the detector wired on the detector socket publishes, with values.threshold and values.blocked_labels, and passes each admitted request through to the upstream unchanged; its rails.co carries the flow that keeps a request body from switching that rail off. Each file is mounted on its own at the path the image's start-up reads, so the guard starts in the product's single-configuration mode and refuses a request naming any other configuration. A NemoGuard model wired on content_safety or jailbreak_detection adds its own input rail. The upstream address is handed to the guard through the MAIN_MODEL_BASE_URL variable it reads, from infra.upstream_endpoint. When the optional upstream_key slot is attached, config.yaml names the variable the credential is delivered under as an env secretKeyRef, so its value never appears in the rendered manifest; unattached, config.yaml names no credential and the guard presents none. The guard answers its health route as soon as it serves, so readiness and liveness both ask it there. provides.host is the bare, self-contained in-cluster service name of the synthesized Service; a consumer in another namespace qualifies it on its own side.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:776f1aa09f0867684714b63bcd7c0c387238bd94f0c6e4075444836a0d6c0ff8
Publicado
2026-11-10T10:25:52Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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:62a1e232ddb42314982a7526650fd9dd47a4f2140f215698556f0b6891395f7f

Referencia en esta versión

oci://hub.aggrega.ai/recipe/helm/nemo-guardrails:1.0.0
Destino
—
Implementa
core/security/nemo-guardrails:1.0.0

Proporciona

Plantillas de punteros deterministas que esta receta cablea para los consumidores.

NombrePlantilla
host{{ .context.rendered_name }}-default
port{{ .infra.port }}
endpointhttp://{{ .context.rendered_name }}-default:{{ .infra.port }}/v1
protocolhttp
threshold{{ .values.threshold }}

Workload

Workload · form: stateless · replicas: 1 · containers: main

Variables locales

NombrePlantilla
config_idconfig
config_dir/app/config/config
upstream_key_variableUPSTREAM_API_KEY
classifier_nameprompt_injection
content_safety_modelcontent_safety

Mapeo de valores

No se declaró ningún mapeo de valores.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

  • implementaimplementacontrato compatible

    core/security/nemo-guardrails:1.0.0

    Todas las salidas obligatorias se satisfacen y cada salida proporcionada está nombrada en el contrato.

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto Recipe →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad