Skip to content
Settings

grpc configuration

cyoda-go version 0.6.2

config.grpc — gRPC listener settings and compute-node credentials.

cyoda exposes a gRPC endpoint for compute-node integration. The listener port is configured via CYODA_GRPC_PORT. External compute nodes authenticate with CYODA_COMPUTE_TOKEN and connect to the endpoint specified by CYODA_COMPUTE_GRPC_ENDPOINT.

  • CYODA_GRPC_PORT — gRPC listen port (default: 9090)

These variables are used by compute-node clients that connect to a running cyoda instance.

  • CYODA_COMPUTE_GRPC_ENDPOINT — gRPC endpoint for the compute node to connect to, e.g. localhost:9090 (required when running as a compute client)
  • CYODA_COMPUTE_TOKEN — bearer token for compute-node authentication (required when running as a compute client)

Server (default port):

CYODA_GRPC_PORT=9090

Compute node client:

CYODA_COMPUTE_GRPC_ENDPOINT=cyoda.internal:9090
CYODA_COMPUTE_TOKEN=my-token
  • config
  • grpc
  • run
  • cyoda help config — Environment variables beat default values. The _FILE suffix variant takes precedence over the plain variable when both are set — for example, CYODA_POSTGRES_URL_FILE=/etc/secrets/db-url wins over CYODA_POSTGRES_URL. There are no command-line flags for configuration values; env vars are the sole configuration surface.
  • cyoda help grpc — cyoda-go exposes one gRPC service: CloudEventsService (package org.cyoda.cloud.api.grpc). All gRPC methods use the CloudEvents Protobuf envelope (io.cloudevents.v1.CloudEvent) as both request and response types. The event type string in the CloudEvent envelope selects the operation; the JSON payload in text_data (or binary_data) carries the operation-specific body.
  • cyoda help run — cyoda-go is a single-process, multi-tenant REST and gRPC API server. It starts in serving mode when invoked with no subcommand. All configuration is via environment variables with a CYODA_ prefix. The binary, Docker image, and Helm chart run the same binary; only the environment configuration differs across run modes.