You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 5, 2021. It is now read-only.
CloudProber running on GKE (Private cluster) fails to initialize due to GCE metadata "instance/name" not defined.
Here the CloudProber logs
I0119 03:27:39.770914 1 logger.go:153] Running on GCE. Logs for cloudprober.sysvars will go to Cloud (Stackdriver).
I0119 03:27:39.790349 1 logger.go:153] Running on GCE. Logs for cloudprober.global will go to Cloud (Stackdriver).
I0119 03:27:39.803867 1 logger.go:153] Running on GCE. Logs for cloudprober.jira-http will go to Cloud (Stackdriver).
I0119 03:27:39.805007 1 logger.go:153] Running on GCE. Logs for cloudprober.stackdriver will go to Cloud (Stackdriver).
F0119 03:27:39.806586 1 cloudprober.go:181] Error initializing cloudprober. Err: unable to retrieve instance name: metadata: GCE metadata "instance/name" not defined
Describe the bug
CloudProber running on GKE (Private cluster) fails to initialize due to
GCE metadata "instance/name" not defined.Here the CloudProber logs
Cloudprober Version
https://hub.docker.com/layers/cloudprober/cloudprober/v0.11.1/images/sha256-27fb01b0ecf1343b0d4c429f4e8ff97edaf687eae501d751f256e958b9432e54?context=explore
To Reproduce
I followed the steps described in here
I also tried the following workarounds:
"--cloud_metadata=none"GCE_METADATA_HOST="metadata.google.internal"Additional context
I'm able to fetch GCE metadata successfully.