NGINX Ingress

Andi Lamprecht ·2026-05-11· 1 min read· Accepted

UTM Nginx Replacement for Kong

Context

UTM is currently using Kong as an ingress controller, not utilizing any of the other features
Kong has to offer.

Kong has proved to be problematic, causing our applications to become unreachable for unpredictable reasons.

Problems

• In most cases, Kong pods get into a crash loop and fail to direct traffic to services.
• In some cases, we will see Kong in a good state but still fails to direct traffic to services.
• When these issues arise, we are not notified until somebody attempts to reach the service.

Temporary Fixes

Deleting bad kong pods fixes the issue every time, but is susceptible to the same problems in the future.

Decision Drivers

• stability
• reliability

Decision

Kong will be replaced with Nginx.

Consequences

• When ingress is updated on a service, it will be unreachable for a few minutes while changes are propagated.