0

我正在尝试在 Kubernetes 1.18 版(托管在树莓派上)下安装 haproxy-ingress。

主节点已正确标记为 role=ingress-controller。

kubectl create 也可以正常工作:

# kubectl create -f https://haproxy-ingress.github.io/resources/haproxy-ingress.yaml
namespace/ingress-controller created
serviceaccount/ingress-controller created
clusterrole.rbac.authorization.k8s.io/ingress-controller created
role.rbac.authorization.k8s.io/ingress-controller created
clusterrolebinding.rbac.authorization.k8s.io/ingress-controller created
rolebinding.rbac.authorization.k8s.io/ingress-controller created
configmap/haproxy-ingress created
daemonset.apps/haproxy-ingress created

但是,该 pod 处于崩溃循环中:

# kubectl get pods -n ingress-controller -o wide
NAME                    READY   STATUS             RESTARTS   AGE   IP              NODE              NOMINATED NODE   READINESS GATES
haproxy-ingress-dpcvc   0/1     CrashLoopBackOff   1          30s   192.168.1.101   purple.cloudlet   <none>           <none>

日志显示该错误:

# kubectl logs  haproxy-ingress-dpcvc -n ingress-controller
standard_init_linux.go:211: exec user process caused "exec format error"

有没有人经历过类似的事情?这可能与我正在使用的 raspbian 的 arm(32 位)架构有关吗?

4

1 回答 1

0

不幸的是,haproxy-ingress 不支持树莓派的 run arm 架构。

于 2020-08-15T02:19:10.703 回答