knative-serving installation failed with missing domainmapping-webhook-cert

[jcheungca]

I am new to kubeflow and hope this is a simple issue. Installl with Juju and all components running fine but knative-serving,

from the log, see the following

{"severity":"ERROR","timestamp":"2023-07-17T20:20:10.346455091Z","logger":"domainmapping-webhook","caller":"webhook/webhook.go:148","message":"failed to fetch secret","commit":"e82287d","knative.dev/pod":"domainmapping-webhook-7d79fb547-jlwg4","error":"secret "domainmapping-webhook-certs" not found","stacktrace":"knative.dev/pkg/webhook.New.func2\n\tknative.dev/[email protected]/webhook/webhook.go:148\ncrypto/tls.(*Config).getCertificate\n\tcrypto/tls/common.go:1064\ncrypto/tls.(*serverHandshakeStateTLS13).pickCertificate\n\tcrypto/tls/handshake_server_tls13.go:363\ncrypto/tls.(*serverHandshakeStateTLS13).handshake\n\tcrypto/tls/handshake_server_tls13.go:55\ncrypto/tls.(*Conn).serverHandshake\n\tcrypto/tls/handshake_server.go:54\ncrypto/tls.(*Conn).handshakeContext\n\tcrypto/tls/conn.go:1460\ncrypto/tls.(*Conn).HandshakeContext\n\tcrypto/tls/conn.go:1403\nnet/http.(*conn).serve\n\tnet/http/server.go:1848"}
2023/07/17 20:20:10 http: TLS handshake error from 172.18.188.137:46110: tls: no certificates configured

Please help.

[jcheungca]

$ k8 get secrets -n knative-serving
NAME TYPE DATA AGE
serving-certs-ctrl-ca Opaque 2 26d
knative-serving-certs Opaque 3 26d

Also, it seems the certificate is missing or failed to generate

[i-chvets]

@jcheungca Could you provide exact steps you followed (or link to the guide) to get to the stage where knative-serving is failing for you?

[DnPlas]

@jcheungca I have tried reproducing the issue by deploying the Charmed Kubeflow 1.7/stable bundle with juju deploy kubeflow --channel 1.7/stable --trust, but for me all knative charms go active and idle.

It's been a while since this issue was first filed, and we have not received the requested information, because of that and the team not being able to reproduce, we are closing it. Feel free to re-open if you run into the same error again.