You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Derive load balancer IP from manually provisioned certificates #302
Currently, we support nudging NodePort services onto Nodes that have certificates provisioned, but we don't support anything similar for LoadBalancer services. That can make them difficult to use for short-lived listeners (like Kafka broker (non-bootstrap) listeners) if you require manually provisioned certificates.
When doing this, don't use a SDP-managed resource (like a KafkaCluster) as the owner, since SDP operators will delete any child objects that it doesn't recognize as having created.
Activity
nightkr commentedon Apr 25, 2025
As a workaround, Kubernetes can be configured to avoid deleting the Listener object by attaching a secondary owner beyond the PVC:
When doing this, don't use a SDP-managed resource (like a KafkaCluster) as the owner, since SDP operators will delete any child objects that it doesn't recognize as having created.