knative / eventing

Event-driven application platform for Kubernetes
https://knative.dev/docs/eventing
Apache License 2.0
1.42k stars 598 forks source link

"x509: certificate signed by unknown authority" was promoted when I installed Channel component. #3618

Closed Benson666 closed 4 years ago

Benson666 commented 4 years ago

Describe the bug I have completed Serving and Eventing compont installation. Like this:

istio-system       cluster-local-gateway-5dfdcd4757-kxx8q   1/1     Running            2          2d22h
istio-system       istio-ingressgateway-5c5f498-cl6vt       1/1     Running            2          2d22h
istio-system       istiod-778658967-h8h9g                   1/1     Running            2          2d22h
knative-eventing   eventing-controller-75b7567ddc-q8fxg     1/1     Running            2          2d20h
knative-eventing   eventing-webhook-5b859fd7f-6mzdn         1/1     Running            2          2d20h
knative-eventing   imc-controller-7d465bddc5-6f69p          1/1     Running            0          82m
knative-eventing   imc-dispatcher-f64dcc94d-5pn7p           0/1     CrashLoopBackOff   20         82m
knative-eventing   mt-broker-controller-d5f96b5b5-4hp88     1/1     Running            2          43h
knative-eventing   mt-broker-filter-5d994fb97f-xstbf        1/1     Running            2          43h
knative-eventing   mt-broker-ingress-769b458fd-hjwf5        1/1     Running            2          43h
knative-serving    activator-77c6776d55-5cnp5               1/1     Running            3          2d22h
knative-serving    autoscaler-656fbc4449-gmvmg              1/1     Running            3          2d22h
knative-serving    controller-7dfdf7947c-gbmzv              1/1     Running            2          2d22h
knative-serving    istio-webhook-5cf8895ff-q96lb            1/1     Running            2          2d22h
knative-serving    networking-istio-5c5dd8c758-q6g8x        1/1     Running            2          2d22h
knative-serving    networking-ns-cert-79746f9779-6kmtj      1/1     Running            2          2d20h

And When I implemented "kubectl apply --filename https://github.com/knative/eventing/releases/download/v0.16.0/in-memory-channel.yaml", I got the message below: Error from server (InternalError): error when creating "in-memory-channel.yaml": Internal error occurred: failed calling webhook "config.webhook.eventing.knative.dev": Post https://eventing-webhook.knative-eventing.svc:443/config-validation?timeout=2s: x509: certificate signed by unknown authority

Then I checked K8s events, I also see message like this: 15m Warning InternalError namespace/kube-system failed to create namespace certificate: Internal error occurred: failed calling webhook "webhook.serving.knative.dev": Post https://webhook.knative-serving.svc:443/defaulting?timeout=10s: x509: certificate signed by unknown authority

Maybe the webhook server used a unknown CA, or there was some wrong config, I don't know.

Expected behavior How Can I solve the problem and let it go work.

To Reproduce Steps to reproduce the behavior.

Knative release version I use kubernetes @1.18.3, knative@0.16

Additional context Add any other context about the problem here such as proposed priority

lionelvillard commented 4 years ago

@Benson666 Can you try deleting the certificates in knative-eventing and knative-serving? Look for eventing-webhook-certs and serving-webhook-certs.

lberk commented 4 years ago

@Benson666 please feel free to reopen this issue if you're still hitting this bug, otherwise we're going to close for now, thanks!