vmware-tanzu/sources-for-knative

vmware-sources webhook CrashLoopBackOff when using VMware TCE on Apple M1

lamw opened this issue · 1 comments

lamw commented

Attempting to deploy Tanzu Application Platform (TAP) 1.1.0 with Cloud Native Runtime (CNR) on Tanzu Community Edition (TCE) on an Apple M1 fails due to webhook container failing in vmware-sources namespace.

Summary

k get pods -A                                                                                                                                       ✔  05:48:35 PM
NAMESPACE              NAME                                                   READY   STATUS             RESTARTS     AGE
contour-external       contour-85f57764b6-47l8l                               1/1     Running            0            5m18s
contour-external       contour-85f57764b6-x54hb                               1/1     Running            0            5m18s
contour-external       envoy-k5h54                                            2/2     Running            0            5m19s
contour-internal       contour-754dcc9bdb-9dzhw                               1/1     Running            0            5m15s
contour-internal       contour-754dcc9bdb-rq282                               1/1     Running            0            5m15s
contour-internal       envoy-brclj                                            2/2     Running            0            5m18s
knative-eventing       eventing-controller-7f977df967-l4f4v                   1/1     Running            0            5m20s
knative-eventing       eventing-webhook-6584f6bf85-lsfzf                      1/1     Running            0            5m19s
knative-eventing       eventing-webhook-6584f6bf85-wf2rv                      1/1     Running            0            5m4s
knative-eventing       imc-controller-7d54ff8fb5-k8tn7                        1/1     Running            0            5m18s
knative-eventing       imc-dispatcher-5c47496b6f-rj89c                        1/1     Running            0            5m18s
knative-eventing       mt-broker-controller-6486444994-hbw2s                  1/1     Running            0            5m17s
knative-eventing       mt-broker-filter-6c68996854-9jhv8                      1/1     Running            0            5m18s
knative-eventing       mt-broker-ingress-6586fb4c6f-vxrxw                     1/1     Running            0            5m18s
knative-eventing       rabbitmq-broker-controller-677bf484b9-hglvm            1/1     Running            0            5m17s
knative-eventing       rabbitmq-broker-webhook-8dff89fd8-wbj9h                1/1     Running            0            5m17s
knative-eventing       sugar-controller-5fd8578999-rtdbb                      1/1     Running            0            5m16s
knative-serving        activator-55dddbb47b-4vsz7                             1/1     Running            0            5m5s
knative-serving        activator-55dddbb47b-fw4rw                             1/1     Running            0            5m5s
knative-serving        activator-55dddbb47b-qclf7                             1/1     Running            0            5m20s
knative-serving        autoscaler-79d499dfc5-qqb26                            1/1     Running            0            5m20s
knative-serving        autoscaler-hpa-d69cd76-gw84q                           1/1     Running            0            5m19s
knative-serving        controller-6c599c6dc8-wwdmz                            1/1     Running            0            5m19s
knative-serving        domain-mapping-84ffc796c7-dhsbb                        1/1     Running            0            5m19s
knative-serving        domainmapping-webhook-5b496f9598-skqnl                 1/1     Running            0            5m19s
knative-serving        net-certmanager-controller-7c9dd4f4cc-tx7rj            1/1     Running            0            5m16s
knative-serving        net-certmanager-webhook-5b86f5489d-m752w               1/1     Running            0            5m16s
knative-serving        net-contour-controller-58c454d494-jv97w                1/1     Running            0            5m15s
knative-serving        webhook-54b8f869c9-blpnj                               1/1     Running            0            5m19s
knative-serving        webhook-54b8f869c9-dbqks                               1/1     Running            0            5m4s
knative-sources        rabbitmq-controller-manager-7cd8d88d6c-dlmn9           1/1     Running            0            5m17s
knative-sources        rabbitmq-webhook-668ccd8455-mhslw                      1/1     Running            0            5m17s
kube-system            calico-kube-controllers-b5d49d4c5-zjjzn                1/1     Running            0            22m
kube-system            calico-node-d8rrl                                      1/1     Running            0            22m
kube-system            coredns-78fcd69978-mxq8s                               1/1     Running            0            23m
kube-system            coredns-78fcd69978-znn65                               1/1     Running            0            23m
kube-system            etcd-m1-tce-cluster-control-plane                      1/1     Running            0            24m
kube-system            kube-apiserver-m1-tce-cluster-control-plane            1/1     Running            0            24m
kube-system            kube-controller-manager-m1-tce-cluster-control-plane   1/1     Running            0            24m
kube-system            kube-proxy-kn65x                                       1/1     Running            0            23m
kube-system            kube-scheduler-m1-tce-cluster-control-plane            1/1     Running            0            24m
local-path-storage     local-path-provisioner-85494db59d-m4j2l                1/1     Running            0            23m
secretgen-controller   secretgen-controller-85644f8f68-kfhzt                  1/1     Running            0            8m53s
tkg-system             kapp-controller-779d9777dc-l5kjd                       1/1     Running            0            23m
triggermesh            aws-event-sources-controller-67478d5b6f-xv42p          1/1     Running            0            5m20s
vmware-sources         webhook-5f647dcdd5-r68sw                               0/1     CrashLoopBackOff   5 (4s ago)   5m16s

Logs

k -n vmware-sources logs webhook-5f647dcdd5-r68sw                                                                                              ✔  3s  05:50:33 PM
2022/04/14 00:49:57 Registering 4 clients
2022/04/14 00:49:57 Registering 3 informer factories
2022/04/14 00:49:57 Registering 10 informers
2022/04/14 00:49:57 Registering 7 controllers
2022/04/14 00:50:02 Error reading/parsing logging configuration: timed out waiting for the condition: context canceled

Environment Details

Client OS:

Darwin Kernel Version 21.4.0: Fri Mar 18 00:46:32 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T6000 arm64

Docker Version:

docker version                                                                                                                                      ✔  05:44:07 PM
Client:
 Cloud integration: v1.0.22
 Version:           20.10.12
 API version:       1.41
 Go version:        go1.16.12
 Git commit:        e91ed57
 Built:             Mon Dec 13 11:46:56 2021
 OS/Arch:           darwin/arm64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.5.0 (74594)
 Engine:
  Version:          20.10.12
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.12
  Git commit:       459d0df
  Built:            Mon Dec 13 11:43:07 2021
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.4.12
  GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Docker Resources:

6 x vCPU
16GB memory

Tanzu CLI Version

tanzu version
version: v0.11.2
buildDate: 2022-03-24
sha: 6431d1d

TCE Version

V0.11.0

k8s Dist/Version

Unmanaged k8s Cluster v1.22.4

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.