binary-and-deployment

What problem does it solve?

Edgion users need a reliable way to start the right binary, pass the correct command-line arguments, choose the proper deployment mode (FileSystem vs Kubernetes vs HA), and pick compatible build feature flags without accidentally misconfiguring the gateway/controller behavior.

Core Features & Use Cases

• Binary entry points & CLI argument reference: Covers edgion-controller, edgion-gateway, edgion-cli, and edgion-center, including their roles and key flags like --work-dir, --config-file, listen addresses, and controller connectivity.
• Work directory and path resolution rules: Establishes deterministic precedence for resolving relative paths via CLI --work-dir > ENV EDGION_WORK_DIR > YAML config > Default (".").
• Common deployment patterns: Documents FileSystem local development, Kubernetes single-instance mode, and Kubernetes HA (leader election + standby behavior), with example configuration fields and topology guidance.
• Cargo feature flags matrix: Explains build-time options for allocator (allocator-jemalloc, allocator-mimalloc, allocator-system) and TLS backend (boringssl, rustls), including mutual exclusion rules and practical implications for Gateway TLS runtime.

Quick Start

Use the binary-and-deployment guide to start edgion-controller with FileSystem mode by pointing --conf-dir to your resource directory, then run edgion-gateway with --server-addr pointing at the controller gRPC address.