base.yaml

template/base.yaml defines the namespace, control-plane permissions, runtime timeouts, image defaults, mounted-file root, datasource mode, and imported catalogs. Review the environment-specific values before starting Dayu.

The runtime-related fields are summarized below; use the checked-out template/base.yaml as the source of truth for image coordinates.

# Base configuration template for dayu system

# Namespace to distinguish different dayu deployments, please modify it when deploying multiple dayu systems in the same kubernetes cluster
namespace: dayu
# levels for container logging in dayu: DEBUG, INFO, WARNING, ERROR
log-level: DEBUG
# specify the downloaded result log file name, if not set, log file name will be generated with timestamps, e.g., RESULT_LOG_DAYU_NAMESPACE_dayu_TIME_2025_11_04_01_46_26.json.gz
log-file-name:
# export/retention controls for result logs and system logs
log-export:
  result:
    # keep the latest N task results in distributor storage to avoid unbounded growth, 0 means no limit
    retention-records: 100000
    # prune stale result records every N writes
    retention-prune-interval: 10000
    # batch size used when generating compressed export files
    batch-size: 500
  system:
    # keep the latest N system snapshots in backend storage, 0 means no limit
    retention-records: 100000
    # compact the append-only store after it exceeds retention by this many records
    compact-interval: 10000
# Backend is the only dayu process allowed to access the Kubernetes API.
backend-rbac:
  service-account: dayu-backend
  role: dayu-backend-runtime-manager
  role-binding: dayu-backend-runtime-manager-binding
  cluster-role: dayu-backend-cluster-observer
  cluster-role-binding: dayu-backend-cluster-observer-binding
# Bootstrap services are still created through Sedna JMES. Application runtime
# workers are always rendered as sedna.io/v1alpha1 RuntimeService resources.
support-crd-meta:
  api-version: sedna.io/v1alpha1
  kind: JointMultiEdgeService
# RuntimeService orchestration and bounded revision retirement.
runtime:
  # Maximum time for one RuntimeService activation batch to reach both Activated and Ready.
  activation-timeout-seconds: 600
  # End-to-end budget for one install, recovery, or redeployment transaction.
  operation-timeout-seconds: 900
  # Total budget for one Scheduler control-plane HTTP call, including retries.
  scheduler-request-timeout-seconds: 30
  # Maximum immutable grace for tasks still using the previous RuntimeDirectory revision.
  retirement-grace-seconds: 180
  # TTL for task reservations, leases, join barriers, and runtime idempotency records.
  lease-ttl-seconds: 3600
# default image meta information for dayu containers, <registry>/<repository>/<image_name>:<tag>
default-image-meta:
  registry: repo:5000
  repository: dayuhub
  tag: current-tag
# default file mount prefix for dayu containers
default-file-mount-prefix: "/data/dayu-files"
# datasource configuration
datasource:
  # true/false, use a simulation datasource container or use a real datasource
  use-simulation: true
  # specify the edge node to run simulated datasource container, only valid when use-simulation is true
  node: edgex1
  # default data root path in datasource container, only valid when use-simulation is true
  data-root: "/data/datasource/"
  # cycle/non-cycle, play mode of the simulation datasource, only valid when use-simulation is true. cycle: loop playing; non-cycle: stop when the data is finished
  play-mode: cycle
# import scheduler policy configurations
scheduler-policies:
  !include scheduler_policies.yaml
# import service configurations
services:
  !include services.yaml
# import result visualization configurations
result-visualizations:
  !include result-visualizations.yaml
# import system visualization configurations
system-visualizations:
  !include system-visualizations.yaml

current-tag represents the image set built from the current checkout. Use the same value when building images and configuring default-image-meta.

The most deployment-specific values are namespace, default-image-meta, default-file-mount-prefix, and datasource. Keep the default RBAC names unless the same cluster contains another Dayu namespace with intentionally separate names. Runtime workers do not need Kubernetes credentials.

The Redis AOF is stored below default-file-mount-prefix/runtime-state/<namespace>/redis on the cloud node. Keep this path writable and durable. Model and datasource files are described in Deploy Mounted Files.

←Back to Template List