Closed Benson666 closed 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
.
@Benson666 please feel free to reopen this issue if you're still hitting this bug, otherwise we're going to close for now, thanks!
Describe the bug I have completed Serving and Eventing compont installation. Like this:
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