SSL Certificate Error: Authentication URL Works, upstream-vhost Returns 400 about ingress-nginx HOT 5 OPEN

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from ingress-nginx.

/remove-kind bug

• If you can get really detailed to the smallest possible info on how to reproduce this, with a step by step instructions list, that readers can copy/paste from on their own Kind or Minikube cluster, it will be really helpful

from ingress-nginx.

Edited the reproduce part.

from ingress-nginx.

@Tobeje thanks for the yaml manifests. helps a lot

• any chance you can replace the yaml manifests with actual kubectl describe outputs
• if you can show kubectl describe , can you show it for all the resources involved
• Can you actually copy/paste the entire curl command as executed
• Can you copy/paste the actual logs of the controller pods
• Can you Add the nslookup command output to show what ip addrsses those involved hostnames resolve to on the client that launches the curl
• Can you also show the nslookup command output from inside a cluster1 pod to show what ip-address those external-svc hostnames resolve to
• A developer will need to see the real flow when curl request hits so since the error is missing cert, then hoping that the diligence of getting k describe and logs makes it a fully triaged problem

Some people are using client certs and occasionally I have seen some issues where people reported using certs like your use case. But I don't recall seeing a issue where cert went missing after config, hence these questions and the ask for detailed info. thanks you very much for helping out

from ingress-nginx.

/triage needs-information

from ingress-nginx.