skills.rest
Pandaala
PandaalaOFFICIAL
Explore all skills by this author →
GitHub

binary-and-deployment

Document startup and deployment guidance for the Edgion four-binary system.

Updated Aug 27, 2026
Search Tags:#deployment#cli#kubernetes#feature flags#edgion#rustls#boringssl
One-click install
npx skills add https://github.com/Pandaala/Edgion --skill binary-and-deployment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: binary-and-deployment
Source: https://github.com/Pandaala/Edgion/tree/main/skills/02-features/01-binary-and-deployment
Command: npx skills add https://github.com/Pandaala/Edgion --skill binary-and-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about binary-and-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Edgion binaries with the correct configuration?▼

To deploy Edgion binaries, you must run the controller, gateway, CLI, and federation center with correct configurations. The system supports FileSystem local development, Kubernetes single-instance, and Kubernetes HA setups, requiring specific CLI arguments and topology fields for each deployment mode.

What is the precedence order for resolving the Edgion work directory?▼

The Edgion work directory resolution follows a strict precedence: CLI --work-dir takes highest priority, followed by ENV EDGION_WORK_DIR, then YAML config, and finally the default current directory ("."). This deterministic rule ensures relative paths are resolved correctly across binaries.

How do I choose between rustls and boringssl TLS backends for the Edgion gateway?▼

Choosing between rustls and boringssl TLS backends for the Edgion gateway is a build-time cargo feature flag selection. The matrix explains mutual exclusion rules and practical runtime implications for Gateway TLS, ensuring you pick compatible build features without misconfiguring behavior.

Does Edgion support Kubernetes HA deployment with leader election?▼

Yes, Edgion supports Kubernetes HA deployment with leader election and standby behavior. The deployment guide documents this topology alongside FileSystem local development and Kubernetes single-instance modes, providing example configuration fields for each setup.

Can I use jemalloc or mimalloc allocators when building Edgion binaries?▼

Yes, you can use allocator-jemalloc or allocator-mimalloc when building Edgion binaries via cargo feature flags. The feature matrix also includes allocator-system, explaining mutual exclusion rules and practical implications for your build-time allocator selection.

What are the key CLI arguments for starting the Edgion controller and gateway?▼

Key CLI arguments for starting Edgion binaries include --work-dir, --config-file, listen addresses, and controller connectivity flags. For FileSystem mode, point --conf-dir to your resource directory for the controller, then run the gateway with --server-addr pointing to the controller gRPC address.

Related Skills

Explore More Software Engineering Skills→
lpjhelderlpjhelder

forge-setup

Install and configure kronon-forge with Node.js and npm.

Community
Intermediate
NickCrewNickCrew
29

api-gateway-patterns

Implement API gateway routing, authentication, and traffic management for microservices.

Community
Intermediate
rohitg00rohitg00
944

k8s-certs

Automate Kubernetes certificate management with cert-manager for issuers and certificates.

Community
Advanced
NimbleBrainIncNimbleBrainInc
2

folk-crm

Route Folk CRM interactions to the correct group, person, or company.

Official
Basic