You may encounter an issue where new ingresses being created (or existing ones being edited) with the included Traefik ingress controller are not being updated properly, or not forwarding to the correct endpoint.
A quick short-term solution to this is to delete the Traefik pods in the kubeaddons namespace, which will cause new ones to deploy automatically. However, new ingresses created/edited after you do this will also have this problem.
The root cause of this issue is caused by malformed certificate secrets associated with the ingresses.
To find whether you have bad ingress secrets, first list them out:
kubectl get ingress -A -o jsonpath='{.items[*].spec.tls[*].secretName}'
For each result (${SECRET}) in the respective namespace (${NAMESPACE}), run the following:
kubectl -n ${NAMESPACE} get secret ${SECRET} -o go-template='{{index .data "tls.crt"|base64decode}}'|openssl x509 -noout -text
If any of your ingress secrets fails that check, remove the associated ingress or replace the secret with a valid certificate/key to resolve the issue.