Closed arlando closed 1 year ago
Hi @arlando !
I think the issue here is that your static IP is in the wrong subnet. Can you try creating it in any other subnet besides the proxy-only one?
The IP address must be from a subnet in the same region as the GKE cluster. You can use any available private subnet within the region (with the exception of the [proxy-only subnet](https://cloud.google.com/load-balancing/docs/l7-internal/setting-up-l7-internal#configure-a-network)). Different Ingress resources can also have addresses from different subnets.
Thank you @spencerhance! That worked!
Hello!
When I try to use the
ingress-gce
to create an internal cloud native HTTP load balancer I get an error the load balancer cannot be created because the purpose of the subnetwork's purpose is notPRIVATE
.I've followed the steps as per the docs https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balance-ingress#console but I can't tell what I'm missing.
First, I created a subnetwork an
INTERNAL HTTPS LOAD BALANCER
in terraform v1.0.3 and the latest google provider:Next, I created a firewall rule to allow traffic from the proxy only subnetwork to my GKE cluster. Finally, I created a static IP within the subnet.
Any reason why this is happening? Note the
7pc1x9ef-default-cool-website-a185lva1
is never created AFAIK. There is no way for me to create a subnetwork with a PRIVATE purpose unless I am misunderstanding something. I've doubled checked and my GKE cluster seems to be created correctly with the right configuration variables. Any advise would be appreciated.