In what area(s)?
/area networking
Ask your question here:
Clean deployments running isio 1.4.
CNI + SDS + Strict mTLS configured
Minimal Serving component installed for knative with cert-manager 0.10 configured with clusterissuer against letsencrypt staging.
For initial testing, I deploy the basic helloworld serving demo which returns:
NAMESPACE NAME URL LATESTCREATED LATESTREADY READY REASON
samples helloworld-go https://helloworld-go.samples.example.com helloworld-go-p9b56 helloworld-go-p9b56 Unknown IngressNotConfigured
LetsEncrypt certificate is created and saved correctly.
Initial pod has all relevant proxy containers injected.
No errors reported within container logs.
knative-ingress-gateway doesn't get updated with the additional host configuration I would expect and looking into the logs for networking-istio pod I have the following lines:
{"level":"info","ts":"2019-12-05T11:50:12.399Z","logger":"istiocontroller","caller":"ingress/ingress.go:436","msg":"Cleaning up Gateway Servers for Ingress helloworld-go","commit":"a1a35b1","knative.dev/traceid":"64d8de38-18f1-4bd7-9c72-e16370724587","knative.dev/key":"samples/helloworld-go"}
{"level":"error","ts":"2019-12-05T11:50:12.410Z","logger":"istiocontroller","caller":"controller/controller.go:357","msg":"Reconcile error","commit":"a1a35b1","error":"failed to update Gateway: Gateway.networking.istio.io \"knative-ingress-gateway\" is invalid: spec.servers.tls.subjectAltNames: Invalid value: \"null\": spec.servers.tls.subjectAltNames in body must be of type array: \"null\"","stacktrace":"knative.dev/serving/vendor/knative.dev/pkg/controller.(*Impl).handleErr\n\t/home/prow/go/src/knative.dev/serving/vendor/knative.dev/pkg/controller/controller.go:357\nknative.dev/serving/vendor/knative.dev/pkg/controller.(*Impl).processNextWorkItem\n\t/home/prow/go/src/knative.dev/serving/vendor/knative.dev/pkg/controller/controller.go:343\nknative.dev/serving/vendor/knative.dev/pkg/controller.(*Impl).Run.func2\n\t/home/prow/go/src/knative.dev/serving/vendor/knative.dev/pkg/controller/controller.go:291"}
It looks like the configuration of gateway by istio-networking is malformed or am I looking in the wrong place?
Thanks.
In what area(s)?
/area networking
Ask your question here:
Clean deployments running isio 1.4.
CNI + SDS + Strict mTLS configured
Minimal Serving component installed for knative with cert-manager 0.10 configured with clusterissuer against letsencrypt staging.
For initial testing, I deploy the basic helloworld serving demo which returns:
LetsEncrypt certificate is created and saved correctly.
Initial pod has all relevant proxy containers injected.
No errors reported within container logs.
knative-ingress-gateway doesn't get updated with the additional host configuration I would expect and looking into the logs for networking-istio pod I have the following lines:
It looks like the configuration of gateway by istio-networking is malformed or am I looking in the wrong place?
Thanks.