Hi Frank,I was just made aware of your post..
affraid its a bit of a known issue..
NOI inserts the namespace into the FQDN/hostnames as a subdomain..
however standard ingress certificates don't support this :-( , as you noticed.
for normal browser activity , that is not a issue.
but it is an issue if you need to interface (SSL) with the solution. e.h. API/Rest calls.
there are 2 solution to this.
1)if it is just API usage that you need. i suggest you copy the "route" that you need. and remove the namespace/subdomain from the new route. (a bit cumbursome if you need multiple routes...-
2) if you need a more permanent option. i suggest you create a new ingress certificate that supports BOTH SAN
but this doesnt say how to create the certificate..
but a hint could be here:
hope it helps..