envoyproxy/gateway

Ability to change caCertificateRefs ca.crt key

Open

#7,567 opened on 2025年11月19日

GitHub で見る
 (12 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
help wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (PR metrics pending)

説明

When creating a BackendTLSPolicy, the caCertificateRefs key is statically set to ca.crt. When using cluster-api to bootstrap workload clusters, the created $CLUSTER-ca secret will have the following keys: tls.crt and tls.key.

Having the ability to set the CA key to tls.crt would support these resources without having to use something like kyverno to add the ca.crt field to the secret.

Similar issue on Gateway API: https://github.com/kubernetes-sigs/gateway-api/issues/4196

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