envoyproxy/envoy

Duplicate custom_cert_validator config is not shared across all users

Open

#38,693 opened on 2025年3月10日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/certificatesarea/configurationenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (平均マージ 8d) (30d で 378 merged PRs)

説明

custom_cert_validator creates duplicate objects for every cluster / listener using it

Description: A proxy processing 100+ clusters takes up to 10 seconds to start up because it has to reload the same custom_cert_validator config being used by all of them.

Repro steps: Configure multiple clusters / listeners with the same custom_validator_config. Each one will be initialized with a unique copy of the config, and each unique copy will be fully processed independently.

Config: This validation context being used by multiple clusters. You can see from the debug logs that it is being parsed N times.

          validation_context:
            custom_validator_config:
              name: envoy.tls.cert_validator.spiffe
              typed_config:
                "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.SPIFFECertValidatorConfig
                trust_domains:
                - name: example.org
                  trust_bundle:
                    filename: "<bundle>"

コントリビューターガイド