Documentation
¶
Overview ¶
Package config loads the proxy MeshConfig (aether.config.v1.MeshConfig) from a YAML document — typically a mounted ConfigMap projected from the MeshConfig CR — validating it with protovalidate. System-wide settings (OTEL, SPIRE, mesh domain) are aether (umbrella-chart) config inherited as flags, not part of MeshConfig; see docs/proposals/015_mesh-config.md.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func Load ¶
func Load(path string) (*configv1.MeshConfigSpec, error)
Load reads, parses and validates a MeshConfig from the file at path.
The pipeline is YAML -> JSON -> protojson (lenient: unknown fields are ignored for forward-compatibility across versions) -> protovalidate. Inheritance of unset proxy overrides from the aether system config is the caller's job (the agent), which is the only place that holds both.
A missing file is NOT an error: the MeshConfig (proxy observability overrides) is optional, so its absence means "inherit everything from the aether system config". This decouples startup from the controller having projected the ConfigMap yet, and lets deployments without a mounted config (e.g. e2e) run.
Types ¶
This section is empty.
Source Files