serving: Activator Pod keep in CrashLoopBackoff

In what area(s)?

/area networking

What version of Knative?

Knative 0.6

Expected Behavior

Install the component of Knative Serving successfully

Actual Behavior

kubectl get pod -n knative-serving
NAME                                READY   STATUS    RESTARTS   AGE
activator-dfdb7f85-mfwhg            1/2     CrashLoopBackoff  15         32m
autoscaler-565cdf546b-hhkm7         2/2     Running   0          32m
controller-78564fd45c-x5mm5         1/1     Running   0          32m
networking-istio-6d95d868fb-tqwqw   1/1     Running   0          32m
webhook-5dc6f74b5b-5xdqv            1/1     Running   0          32m

Steps to Reproduce the Problem

Install Kubernetes 1.13

Install Istio 1.1.3

kubectl get pod -n istio-system 
NAME                                      READY   STATUS      RESTARTS   AGE
grafana-749c78bcc5-vtdm4                  1/1     Running     0          4h19m
istio-citadel-899dfb67c-7w5lz             1/1     Running     0          4h19m
istio-egressgateway-748d5fd794-khlm2      1/1     Running     0          4h5m
istio-egressgateway-748d5fd794-xddj4      1/1     Running     0          4h19m
istio-galley-555dd7c7d7-dffls             1/1     Running     0          4h19m
istio-ingressgateway-55dd86767f-lpp9w     1/1     Running     0          4h19m
istio-pilot-7979d58649-ffwjt              2/2     Running     0          4h19m
istio-pilot-7979d58649-lbqfv              2/2     Running     0          4h3m
istio-policy-f89c945dc-pfct8              2/2     Running     0          4h19m
istio-sidecar-injector-998dd6cbb-w5428    1/1     Running     1          4h19m
istio-telemetry-7d9d866c65-dw8mq          2/2     Running     0          4h19m
istio-tracing-595796cf54-zmqdb            1/1     Running     1          4h19m
kiali-5df77dc9b6-dlztz                    1/1     Running     0          4h19m
prometheus-7f87866f5f-gdl95               1/1     Running     1          4h19m

Install Knative Serving

kubectl apply --selector knative.dev/crd-install=true  --filename serving.yaml
kubectl apply --filename serving.yaml  --selector networking.knative.dev/certificate-provider!=cert-manager

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 31 (12 by maintainers)

Most upvoted comments

after further looking into our issue, it seems to be related with sidecar container resources limit for activator and autoscaler. Apparently the default 128Mi memory for sidecar container isn’t enough with 450 ksvc workload. we bumped those limit by adding annotations to the PodSpec of their deployments: sidecar.istio.io/proxyCPU: 500m and sidecar.istio.io/proxyMemory: 512Mi. After that both autoscaler and activator are up and running.

patrickshan on Jun 20, 2019