There are two problems in how SDS updates are published:
-
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.
-
When an update fails to a cert, all other subsequent certs in the same recipient are not populated.