This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Gari Singh is a Product Manager at Google Cloud focused on Google Kubernetes Engine (GKE). He spends a majority of his time promoting containers, Kubernetes and GKE and works with multiple GKE customers across all industries.
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 ...
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.
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: