[kube-up][scale-out] event-exporter pod stuck in CrashLoopBackOff state

[h-w-chen]

What happened:
after kube-up scale-out cluster started, from tp-1 master node,

kubectl get pod -AT -l k8s-app=event-exporter
TENANT   NAMESPACE     NAME                                     HASHKEY               READY   STATUS             RESTARTS   AGE
system   kube-system   event-exporter-v0.2.5-868dff6494-q4xs5   2742064492252183928   0/1     CrashLoopBackOff   6          21m

What you expected to happen:
pod in Running state

How to reproduce it (as minimally and precisely as possible):
start 1 tp, 1 rp w/ 1 worker node scale-out cluster via kube-up.sh (code from poc-2022-01-30, with pr1320 cherry-picked)

Anything else we need to know?:

Environment:

• Arktos version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools: kube-up scale-out (1 tp +1 rp x1 worker)
• Network plugin and version (if this is a network-related bug):
• Others:

[h-w-chen]

pod log

{"log":"F0204 20:51:24.842859       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-04T20:51:24.843226811Z"}

[Sindica]

Check whether this is service related.

[teoxrr]

@h-w-chen Did you solve that?