Esta página foi traduzida automaticamente. Leia o original em inglês.

Recipe

tyk

Tyk Gateway on Kubernetes via the open-source stack chart the gateway's own maintainers publish, served from the project's HTTPS chart repository. The chart was chosen over a hand-authored workload because it meets all three conditions the catalog asks of a chart: it is official, published by the product's maintainers alongside the gateway itself; it is complete, carrying the gateway Deployment, its Service, the storage wiring and the directory setup the gateway needs at start; and it is maintained, its most recent release post-dating the most recent gateway release by two days as read on 2026-09-20. The chart bundles three components — the gateway, an analytics purger, and the vendor's Kubernetes controller — and only the gateway is unconditional. This Recipe deploys the gateway alone: the purger and the controller stay off, and the controller's configuration secret, which the chart emits by default even with the controller off, is turned off too, so the render carries nothing belonging to a component this Recipe does not stand up. The chart names its generated resources after the release, so fullnameOverride is bound to the release name the helm provider gives the chart, which spells the component's name in the alphabet a Kubernetes name allows, and provides.host names the Service the chart emits. It writes each core/upstream-key-pinning attachment into the gateway's environment. A cache publishing valkey-tls or redis-tls is reached through the chart's own Redis TLS setting, checked against the cache connection's server_ca, mounted, or the image's trust store; another TLS protocol halts the build. Default chart version in source.version; override via infra.source_version.

Procedência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como publicador oficial.
Digest do conteúdo
sha256:b457135ca0920bdad2967239b3b4f8662c5da607ddfef232abf99e5164b3f062
Publicado
2026-11-10T10:27:46Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • 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:b89703ae5fbc2a1c1f484e8c1e18398a3e906d9e25fd685333c2d67c6347375d

Referência nesta versão

oci://hub.aggrega.ai/recipe/helm/tyk:1.0.0
Destino
—
Implementa
core/gateway/tyk:1.0.0

Fornece

Modelos de ponteiros determinísticos que esta receita liga para os consumidores.

NomeModelo
hostgateway-svc-{{ .context.rendered_name }}
port{{ .infra.port }}
protocolhttp

Workload

Nenhum modelo de carga de trabalho declarado.

Variáveis locais

Nenhuma variável local declarada.

Mapeamento de valores

Nenhum mapeamento de valores declarado.

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é exibida como uma aresta quebrada em vez de um link.

Usa

  • implementaimplementacontrato compatível

    core/gateway/tyk:1.0.0

    Todas as saídas obrigatórias são atendidas e cada saída fornecida é nomeada no contrato.

Usado por

Nada no catálogo depende desta entidade.

Referência do conceito Recipe →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design compartilhado do Aggrega.

Privacidade