About garisingh

garisingh

See https://www.googlecloudcommunity.com/gc/Google-Kubernetes-Engine-GKE/Gateway-API-opens-0-65535-TCP-ports-for-HealthChecks-even-though/m-p/771986/highlight/true#M2145 You can create your own custom firewall rules and set them to a higher priority ...

garisingh

You can create your own firewall rule(s) with a higher priority than 1000 (which is the priority used by the automatically generated rules).

garisingh

You cannot rename / set a name for them.

garisingh

It's not like the ports are wide-open to the world. Access to the ports is limited to the Google ranges for load balancers as well as any proxy subnet range you create.

garisingh

The error itself is an odd one and isn't actually indicative of anything. It's being looking into, but in the meantime, you can create a log exclusion filter to avoid the log messages / costs:

My Stats

garisingh's Bio

Badges garisingh Earned

Recent Activity

Re: GKE gateway API: Control open ports on default firewall rule

Re: Gateway API opens 0-65535 TCP ports for HealthChecks even though only the port 80 is ever used

Re: Rename Load Balancers automatically created by GKE Ingress Controller

Re: Gateway API opens 0-65535 TCP ports for HealthChecks even though only the port 80 is ever used

Re: Cloud Autoscaling API Errors 100%