envoyproxy/envoy

Native multi-file YAML config support like Nginx `include` directive

Open

#43,511 创建于 2026年2月16日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)C++ (27,997 star) (5,373 fork)batch import
enhancementhelp wanted

描述

Feature Request Summary

Add native support for splitting Envoy bootstrap configuration across multiple YAML files, similar to Nginx's include directive and /etc/nginx/conf.d/*.conf directory scanning.

Motivation

Unlike Nginx, which seamlessly loads multiple config files from a directory into a unified config tree, Envoy requires a single bootstrap YAML file. Current workarounds like !ignore YAML fragments with anchors/aliases work but have limitations:

  • Still requires a "main" bootstrap file
  • Manual anchor management across files
  • No automatic directory scanning
  • Full reload needed for fragment changes
  • Not as intuitive for teams familiar with Nginx/HAProxy

This is especially painful for complex deployments (Kubernetes sidecars, Docker Compose with multiple services) where configs grow large and need modularization.

贡献者指南

技术栈
cpp
领域
backenddevops
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Envoy bootstrap configC++YAML parsingFile system operations
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
Examine the existing bootstrap configuration loading mechanism in Envoy, particularly the YAML parsing and validation code in source/server/config * files. Look at how the main configuration file is read (e.g., ConfigImpl::loadBootstrapConfig) and consider how to extend it to support multiple files via an include directive. Refer to Nginx's include implementation for inspiration. Engage with maintainers in the issue comments to clarify desired API, syntax, and constraints such as override semantics and directory scanning.