[kube-up][scale-out] l7-default-backend pod is in CrashLoopBackOff state

[h-w-chen]

What happened:
in kube-up scale-out 1+1x1 cluster, on tp-1 master:

$ kubectl get pod -AT -l k8s-app=glbc
TENANT   NAMESPACE     NAME                                  HASHKEY               READY   STATUS             RESTARTS   AGE
system   kube-system   l7-default-backend-6497bc5bf6-qpdv8   5056521056879339513   0/1     CrashLoopBackOff   9          32m

What you expected to happen:
pod in Running state

How to reproduce it (as minimally and precisely as possible):
start 1+1x1 scale-out cluster by kube-up.sh (at branch poc-2022-01-30 with PR 1320 cherry picked);
at TP-1 master, run kubectl get pod -AT -l k8s-app=glbc

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+1x1
• Network plugin and version (if this is a network-related bug): mizar cni
• Others:

[h-w-chen]

pod log

{"log":"I0205 00:15:48.456867       1 server-with-metrics.go:61] Default 404 server is running with GOMAXPROCS(4) on l7-default-
backend-6497bc5bf6-qpdv8:8080\n","stream":"stderr","time":"2022-02-05T00:15:48.457163941Z"}

[Sindica]

Existing issue with default cluster up.