I am trying to setup Set up an external HTTP(S) load balancer with Ingress on default network but I am getting this error
Error syncing to GCP: error running load balancer syncing routine: loadbalancer hir11den-default-fanout-ingress-vrxp3k5k does not exist: googleapi: Error 400: STANDARD network tier (the project's default network tier) is not supported: STANDARD network tier is not supported for global forwarding rule., badRequest
I am attaching the error page
here is my fanout-ingress.yaml file :-
GKE Ingress (and Gateway) resources do not currently support STANDARD tier networking. STANDARD tier is supported for L4 load balancers (Service with type LoadBalancer) using the following annotation
cloud.google.com/network-tier: Standard
I have checked the network tier it is standard I guess , do I need to change this to premium and if I change it to premium can I change it back to standard tier.
You would need to change this to Premium if you want to deploy the HTTP(s) load balancer(s) via Ingress or Gateway resources. I'll double-check, but I don't think you can change it back as you may run into issues when updating the Ingress / Gateway in the future. Premium is only requires for the L7 HTTP(s) load balancers. If you want to use the L4 load balancer instead, you can use the annotation above on the Service and stay on Standard tier.
If you want to use an L7 load balancer and are ok not using Ingress to configure it, you can manually create the load balancer directly and then use GKE standalone NEGs and attach them to the load balancer.
We are working to add support for Premium tier for regional external load balancers, hopefully over the next couple of months.
If I create L7 load balancer directly and use GKE standalone NEGs and attach them to the load balancer without , what will be the lose , can I still able to route the traffic correctly using host and path rules from L7 LB without ingress.