envoyproxy / envoyproxy/envoy

sds: early update failure can stop secret updates

Open
#42,438 1 comment 1 reaction 1 assignee Claimed by @kyessenov View on GitHub
bug no stalebot
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 22h
Merged PRs (30d)
430

Description

There are two problems in how SDS updates are published:

1) When a cluster/listener is attached to a subscription, and the current cert is incompatible with it (e.g. wrong proto or private key method cannot bind), then no future SDS updates will be sent to that recipient.

2) When an update fails to a cert, all other subsequent certs in the same recipient are not populated.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.