Subdomain wildcard certificate domains not working with HTTPS about kubernetes-ingress-controller

[pawandhiman10]

It displays this certificate.

[programmer04]

Hey @pawandhiman10, for what you described a dedicated test has been added and it seems there is no issue with KIC and Kong

• #6310

What you describe boils down to making requests with a properly set host, so in the case of curl it has to be done like that (assuming that the certificate is trusted)

 curl https://test.example.com --resolve test.example.com:443:172.18.128.3      

read more in the docs.

Otherwise, when you try to access https://172.18.128.3 directly e.g. with curl or browser it won't have any routes in Kong and it leads to presenting a default certificate as you pointed out #6216 (comment). To access such domain properly with a browser on your machine you can add an entry for test.example.com to /etc/hosts and then use https://test.example.com in a browser. The right certificate will be presented and traffic will be routed to a proper service