after upgrading to ingress-nginx version 4.13.2, UI not loading-getting 400 bad request (The plain HTTP request was sent to HTTPs port) nginx

[Geeshma-n]

after upgrading to ingress-nginx version 4.13.2, UI not loading-getting 400 bad request (The plain HTTP request was sent to HTTPs port) nginx

UI is working/loading until versions 4.11.8.

[k8s-ci-robot]

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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Gacko]

Have you tried a fresh install? What you are describing sounds like you didn't re-use your Helm values and misconfigured the upgraded version. Or you had something configured in the ConfigMap manually and did not pass these as values to your Helm command.

[Geeshma-n]

for this upgrade export BD4BS_NGINX_INGRESS_CHART_VERSION=4.11.5 (current version)
was updated to export BD4BS_NGINX_INGRESS_CHART_VERSION=4.13.2. (target version)

we tested with all the versions until 4.11.8, we were getting expected output & worked fine.
from 4.12.0 version onwards getting these 400 bad request errors

except the above update, no other changes were made & nothing was configured in the ConfigMap manually.

[Gacko]

Have you read the release notes of Ingress NGINX Controller v1.12.0 / Chart v4.12.0 thoroughly? We reduced the default value of the maximum accepted annotations risk level from Critical to High, so any configuration snippets will be ignored. If your functionality relies on configuration snippets, then please increase the annotations risk level back to Critical and read the release notes for any other changes.