LiteSpeed Ingress Controller

Overview

LiteSpeed Ingress Controller brings Kubernetes ingress to LiteSpeed Web ADC, a software load balancer and application delivery controller that can run on dedicated hardware, hosted infrastructure, or cloud. It suits operators who want Gateway API support alongside caching and Web ADC monitoring; the main trade-off is taking responsibility for its broad default exposure and routing behavior.

Key features

Helm installation and native ingress avoid sidecars and Kubernetes modifications, while ZeroConf lets configuration changes take effect without restarting the load balancer. That is a practical fit for teams seeking a direct integration and fewer interruptions during routine changes. The controller supports the Kubernetes Gateway API as well as Ingress definitions.

Support for all HTTP versions, including HTTP/2 and HTTP/3, plus WebSockets, covers modern web traffic. Built-in LiteSpeed Cache is designed to accelerate web applications. Canary routing, rate limiting, authentication policies, and TLS automation add useful traffic and security controls. The Web Application Firewall can use familiar ModSecurity rules and templates, though teams should account for configuring those policies to their needs.

Realtime statistics and controller commands are available in the Web ADC WebAdmin Console. Helm-based Kubernetes installation includes full 24-7 support. For HTTPS, the documentation recommends Kubernetes cert-manager to manage TLS secrets. One operational point deserves attention before deployment: by default, the LiteSpeed LoadBalancer is exposed to the internet and load-balances all Ingress definitions. Teams that need narrower exposure or selective routing should plan for that behavior rather than assuming a private or restricted default.

Web ADC works with all web servers, although LiteSpeed Web Server is preferred on the backend. The controller is part of the broader Web ADC solution, so it is best considered by teams prepared to adopt that delivery layer rather than as an isolated ingress component.

Pricing

The product is described as freemium, with a free trial, but there is no free plan. Paid Web ADC plans start at $65 a month, billed monthly, for one worker. The price note says $10/mo, but the listed plans begin at $65 a month; buyers should budget from the actual worker plans below.

PlanPriceWorkersBest suited toWeb ADC Small$65 a month, billed monthly1A single-worker deploymentWeb ADC Medium$130 a month, billed monthly2A deployment requiring two workersWeb ADC Large$260 a month, billed monthly4A four-worker deploymentWeb ADC Ultimate$520 a month, billed monthlyConfigurableTeams that need configurable worker capacityEach step up buys more worker capacity, not a different stated feature set. Small keeps the monthly commitment lowest but limits the deployment to one worker; Ultimate is the choice when a fixed worker count is unsuitable, at the highest listed price. No trial duration is given, so confirm the trial terms before relying on it for an extended evaluation.

Platforms

The deployment model is self-hosted, with Linux, FreeBSD, macOS, and Solaris supported; the broader platform list also includes web. Windows is not supported. The software can run on private dedicated hardware, hosted environments, or in the cloud, giving operators infrastructure flexibility without making it a Windows option.

Who it's for

This is a stronger fit for Kubernetes teams that value HTTP/3, Gateway API support, cache acceleration, ModSecurity-compatible WAF rules, and round-the-clock installation support. It is less suitable for teams seeking a free production tier, Windows deployment, or defaults that keep ingress private and narrowly scoped without additional planning.

Pros and cons

Pro: HTTP/3, HTTP/2, WebSockets, canary routing, rate limiting, auth policies, and TLS automation cover a broad set of ingress needs.

Pro: ZeroConf applies configuration changes without restarting the load balancer, reducing disruption from routine Kubernetes updates.

Pro: Built-in caching and a ModSecurity-compatible WAF bring acceleration and familiar rule support into the Web ADC.

Con: The default installation exposes the load balancer publicly and routes all Ingress definitions, so operators must review exposure and routing before installation.

Con: There is no free plan, and the lowest listed worker plan costs $65 a month, billed monthly.

Con: Windows is unsupported, ruling it out for Windows-based deployments.

Alternatives

For a broader comparison, see Kubernetes Ingress Controllers. Choose ngrok instead if a free plan with up to three online endpoints and 1GB data transfer suits the use case. Kusk Gateway is a free, MIT-licensed option for teams seeking an open-source gateway.

Traefik Proxy is a free open-source ingress controller, reverse proxy, and load balancer with service auto-discovery. Airlock Microgateway offers a free Community Edition for small environments or local development, with enforced throughput and six-month license validity. BFE Ingress Controller is a free Apache 2.0-licensed option with no plan limits stated. agentgateway is a free open-source gateway deployable as a binary, Docker image, or Kubernetes workload.

Higress offers a free self-hosted Community Edition with community support and documentation, while users handle stability and performance. Contour is a free open-source Kubernetes ingress controller backed by community support.

Verdict

Choose LiteSpeed Ingress Controller if your Kubernetes deployment needs HTTP/3, caching, Web ADC monitoring, and a supported Helm installation, and you can plan carefully around public exposure and all-Ingress routing defaults. Look elsewhere if a free plan, Windows support, or tighter default ingress boundaries matter more than its integrated Web ADC feature set.