You are deploying an application to Cloud Run. Your application requires the use of an API that runs on Google Kubernetes Engine (GKE). You need to ensure that your Cloud Run service can privately rea

Question

Options

• ADeploy an ingress resource on the GKE cluster to expose the API to the internet. Use Cloud
• BCreate an egress firewall rule on the VPC to allow connections to 0.0.0.0/0 on ports 80 and 443.
• CCreate an ingress firewall rule on the VPC to allow connections from 0.0.0.0/0 on ports 80 and
• DDeploy an internal Application Load Balancer to expose the API on GKE to the VPC. Configure

• A
  23% (6)
• B
  8% (2)
• C
  12% (3)
• D
  58% (15)

Explanation

This approach follows Google-recommended practices: Internal Application Load Balancer (ILB): By deploying an ILB on GKE, the API is only accessible within your Virtual Private Cloud (VPC), ensuring private connectivity. Cloud DNS Configuration: Using Cloud DNS with the ILB's IP address allows you to resolve a fully qualified domain name (FQDN) for the API, making it easier to manage and maintain. Serverless VPC Access Connector: Deploying this connector enables your Cloud Run service to communicate with resources in your VPC (such as the internal API on GKE) via private IP

No community discussion yet for this question.