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
What happened:
start scale-up with mizar using kube-up.sh, event-exporter crashloopbackoff with error:
{"log":"F0224 00:29:21.335208 1 main.go:75] Failed to initialize sink: failed to build sink config: not running on GCE, which is not supported for Stackdriver sink\n","stream":"stderr","time":"2022-02-24T00:29:21.33556028Z"}
$ kubectl get pods -AT | grep event-exporter
system kube-system event-exporter-v0.2.5-868dff6494-h4hw4 4772125109102601041 0/1 CrashLoopBackOff 26 118m
What you expected to happen:
event-exporter start successfully How to reproduce it (as minimally and precisely as possible):
ubuntu is missing cloud logging agent, cloud monitor agent. these need be installed to support event-exporter;
Event-exporter requests metadata.onGCE to be true. debug to metadata.onGCE and found this is trying to LookupHost(ctx, "metadata.google.internal"), support for internet access in pods is still in progress based on issue [kube-up][scale-out] pod unable to access internet IP address #1373
What happened:
start scale-up with mizar using kube-up.sh, event-exporter crashloopbackoff with error:
What you expected to happen:
event-exporter start successfully
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: