Hard coded metadata endpoint breaks logging under GKE managed Istio #7517
Labels
api: logging
Issues related to the Cloud Logging API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Environment details
metadata
hostname is present there too).Steps to reproduce
(please bear with me, I do get to the point!)
istio-inejction: enabled
to the default namespace to allow istio to control traffic on workloads deployed there.kubectl run -i --tty busybox --image=busybox --restart=Never -- sh
)metadata
.This is the result of Istio's default policy of blocking all outbound requests until they are whitelisted.
Since istio/istio#10694 will not accept non FQDN's the hardcoded metadata endpoint in the python logging client fails.
This manifests as logs showing up in stackdriver without the expected GCE / GKE annotations of instance name, cluster name, etc.
The approach from other google libraries (eg. googleapis/google-cloud-java#4269 ) is to update to the fully qualified
metadata.google.internal
or just hit the magic IP address directly which Istio has no problems whitelisting.The text was updated successfully, but these errors were encountered: