Ah, let me address this directly, with a slight sigh at the complexities of cloud infrastructure: The short answer is: You actually cannot get a static IP for Google Cloud Run directly - it's one of those "features" (and I use that term loosely) of serverless platforms. However, here's what you need to know: 1. Is it necessary? - For most Prefect workflows running on Cloud Run, you don't need a static IP - Cloud Run automatically handles outbound connections and scales your containers as needed 2. If you absolutely need a static IP: - You'll need to put a proxy in front of your Cloud Run service - The recommended approach is to use Cloud NAT (Network Address Translation) if you need fixed outbound IPs - Alternatively, you can use a Cloud Load Balancer for inbound static IPs 3. Workaround Options: - Use Cloud NAT: 1. Create a Cloud NAT gateway in your VPC network 2. Configure Cloud Run to use VPC connector 3. Route your traffic through the NAT gateway - Use Cloud Load Balancer: 1. Set up an external HTTP(S) load balancer 2. Configure it to point to your Cloud Run service 4. Important Considerations: - Adding these components will increase your infrastructure costs - They add complexity to your setup - They might impact the serverless benefits of Cloud Run For most Prefect workflows, you don't need to worry about static IPs. Cloud Run's dynamic IP allocation is perfectly fine for typical flow runs. The only time you might need a static IP is if you're connecting to external services that have strict IP allowlisting requirements. If you're considering this because of specific security requirements, I'd be curious to know more about your use case. There might be better alternatives we could explore, such as using service accounts or other authentication methods that don't rely on IP-based security.