Blog
Home

If you have http and https ingresses with the same hostname -> Don't use F5 OSS nginx ingress controller!

24 February 2026 · 44 views

AKS Ingress migration War Story: Update #2 – Rolled back to community NGINX after F5 OSS disappointment.

Spent the afternoon uninstalling F5 NGINX Ingress OSS and restoring my original community ingress-nginx setup. It works again (same-host HTTP + HTTPS without splits/forced redirects).

Why the rollback? F5 version's strict host collision + master/minion requirement clashed hard with mixed HTTP/HTTPS on one domain. We need one hostname to serve both http and https api's.

Next (and hopefully last): Traefik ingress controller. It merges same-host rules from multiple Ingresses natively, supports separate TLS/non-TLS Ingresses for the same host without auto-redirects, and has powerful middlewares for custom 307 logic or TCP.

Co-authored with Claude.

If this was useful, you can buy me a coffee.

New articles: follow via RSS.

Related articles

Comments

← All articlesView as Markdown