Assistance Required: Issue with Migration to F5 nginx-ingress Controller from Kubenetes ingress-nginx Controller

[khopithan]

Hi all,

I would appreciate any assistance in resolving an issue encountered during an ingress controller migration.

I currently have a Kubernetes cluster running with the open-source ingress-nginx controller, which has been functioning correctly. Due to the announced retirement of the open-source ingress-nginx, I planned to migrate to the F5 NGINX Ingress Controller.

Steps completed so far:

1. Uninstalled the old ingress-nginx release via Helm.
2. Updated new service annotations to align with F5 NGINX Ingress Controller requirements.

Below shown are the old ingress-nginx annotation values for one of my service,

And these are the new annotations for F5 nginx-ingress controller,

When attempting to access the site via HTTPS, I encounter the following error:,

curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed). More detail may be available in the Windows System event log.

I have verified the ingress controller logs and the certificates. The certificate has been correctly issued and appears valid.

Interestingly, when I use the old ingress-nginx annotations with the new F5 NGINX Ingress Controller, HTTPS access works successfully.

I have been troubleshooting this issue for the past few days and would greatly appreciate any guidance or solutions to resolve this SSL/TLS handshake problem with the F5 NGINX Ingress Controller.

Thank you in advance for your support.

Regards,
Khopithan

[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.

Details

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]

This is the issue tracker of the Open Source variant of Ingress NGINX, please file your issue at the F5 issue tracker.