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

Component

core/compute/server

A generic long-running server primitive. It adds no fields of its own; what it contributes is its operational type, `server` — long-running, stateless compute that expects inbound application traffic. An Aggregate declares this for a component that stays up and serves requests, rather than `worker`, with zero inbound application ports, or the run-once `task`. On a Kubernetes cluster it is a Deployment behind a ClusterIP Service. In an AWS account with an ECS cluster and a VPC, terraform/server-ecs and cloudformation/server-ecs run it as an Amazon ECS service on Fargate. In a Google Cloud project with a VPC network, terraform/server-cloud-run runs it as a Cloud Run service; in an Azure subscription with a Container Apps environment, terraform/server-container-apps as a container app. On Docker Compose, compose/server runs it, publishing no host port unless asked. The catalog pins no image, so nothing renders until the Release sets `infra.image`. The image is the Release's own code, so an edge from this component delivers what its `inject:` block dictates, and no declared socket narrows the mechanism: `env` entries become variables on every realization, `file` entries files everywhere but on Amazon ECS and Cloud Run, and `arg` or any other mechanism is refused by name, as no realization renders a command line. The component's own `inject:` block takes `env` entries too. A `core/secret-value` attachment's value is written into the rendered workload in the clear on every realization, and on Docker Compose so is a `core/referenced-secret` attachment's origin; no other realization delivers one, none delivers `core/random-password`, and the helm realization refuses either by name.

Versión

1.0.01.1.0

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:bdaffb56584849a2e4ed1b7edba2e16d2b319fbfb8f5d37e768d2205c78784b4
Publicado
2026-11-15T08:08:59Z
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:3b0acfa932096664bbb18ab36bf510be96a8e8e8ff1ab77c1ce948f7b7dec212

Referencia en esta versión

oci://hub.aggrega.ai/component/core/compute/server:1.1.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

Extiende BaseComponents#/schemas/BaseComponentParameter

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
imagestring—noContainer image serving the application.
portinteger (min 1024, max 65535)8080noPort the container listens on. On Kubernetes the fronting Service carries inbound traffic to it; on Amazon ECS it is the container port a load balancer target group the Release names sends traffic to; on Cloud Run it is the port requests are sent to, which the container is also handed as PORT; on Container Apps it is the ingress's target port, which the container is also handed as CONTAINER_APP_PORT; on Docker Compose it is the port the service answers at on the Compose network, and the one infra.published_port forwards to.
published_portinteger (min 1024, max 65535)—noPort published on the host's loopback address, 127.0.0.1, on Docker Compose, forwarding to infra.port inside the container; any process on this machine can reach it there. Unset, nothing is published. Kubernetes realizations refuse it; reach the Service with kubectl port-forward, or attach core/public-ingress.
replicasinteger (min 1)1noReplica count, the number of tasks on Amazon ECS, of instances on Cloud Run and of replicas on Container Apps, up to 300 there. The floor is one, because a server that expects inbound traffic has nothing to hold a request while it is at zero. Docker Compose runs one container and refuses a count above one.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads: the Amazon ECS realizations read the cluster, subnets, security groups and roles the service runs under, each under its target's own spelling (subnet_ids on terraform, Subnets on CloudFormation), the Cloud Run realization the project, region, VPC network and service account the service runs in, the Container Apps realization the environment and resource group the app runs in and the identities and registry it pulls with, and the Kubernetes and Docker Compose realizations read none of its keys.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

No se declararon valores de salida.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

No se declararon sockets uses.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

No se declararon slots de acoplamiento.

Lista de permitidos de autoinyección

env

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

Usado por

Referencia del concepto Component →

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