Hi @knet , the issue has been resolved, and I appreciate your adjustments on your end. Upon reviewing our setup, we identified that the mistake was using a network tag for our firewall rule instead of a subnet when configuring for direct VPC connections. To address this, we updated the firewall rule to utilize the subnet IP range as the "source filter" instead of the network tag. Initially, we didn't consider the firewall as the cause because some service instances connected successfully via direct VPC despite network tags potentially not being supported in ingress rules for direct VPC connections
LinkedIn
Twitter
