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
Problem description:
We want to access the Source Stream via external IP. Creating a LoadBalancer via the Deployer properties works to an extend. If we redeploy the Stream the IP is changing. That is a problem since we want to apply a internal domain name to that source. Without being able to attach an static IP this is not possible.
Solution description:
Allow the loadBalancerIP property in the Deployer properties
Description of alternatives:
Maybe deploying an Ingress besides the LoadBalancer and giving having ingressAnnotations (similar to podAnnotation properties) might work, too.
@xetra11. We recommend handling this with the help of an explicit LoadBalancer (LB) configuration that remains static regardless of whatever happens to your application. Along with the label selector support we have in the K8s-deployer, you'd then be able to use the deployer.<yourapp>.kubernetes.deploymentLabels property to pass the label included in the LB, so the traffic can be routed predictably.
Problem description:
We want to access the Source Stream via external IP. Creating a LoadBalancer via the Deployer properties works to an extend. If we redeploy the Stream the IP is changing. That is a problem since we want to apply a internal domain name to that source. Without being able to attach an static IP this is not possible.
Solution description:
Allow the
loadBalancerIP
property in the Deployer propertiesDescription of alternatives:
Maybe deploying an Ingress besides the LoadBalancer and giving having
ingressAnnotations
(similar to podAnnotation properties) might work, too.Additional context:
The text was updated successfully, but these errors were encountered: