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
Fix Kafka connectivity: Use DNS name instead of container IP for Aspire network
ROOT CAUSE: Flink jobs were using Kafka container IP (e.g., 172.18.0.9:9093) which doesn't work in Aspire-managed Docker networks. Aspire creates networks with DNS support where containers communicate using service names.
SOLUTION: Changed GetKafkaContainerIpAsync() to return "kafka:9093" instead of discovering container IP. This allows Flink TaskManager to connect to Kafka using DNS resolution within the Aspire Docker network.
This fixes Exercise1 and Exercise2 Kafka connectivity issues where jobs would submit but produce no output.
Co-authored-by: devstress <30769729+devstress@users.noreply.github.com>
0 commit comments