Kvindo™ Cloud Docs


Language

HTTP Listener

An HTTP Listener accepts inbound HTTP connections on one or more ports of a Load Balancer and routes each request to a Target Group according to its HTTP Listener Rules. It is a Layer-7 listener — it can match on host and path and rewrite headers.

Key concepts

• Load balancer — the LB this listener belongs to (spec.loadbalancerId)

• Interface — which side to bind: all, public, or private — no server-side default; the console preselects all

• Ports / Hosts — the ports to accept on, and the host(s) to match — both required

• Security rules — optional IP allow/deny list applied before routing

Parameters
UI Name API / kc name Terraform name Optional Format Default Is read only Description
Load balancer spec.loadbalancerId spec.loadbalancer_id No ULID — references a Load Balancer — No The load balancer this listener belongs to
Interface spec.interface spec.interface No string — all / public / private — No Which network interface to bind on. No server-side default — the console preselects all for convenience, but the API rejects a missing/empty value
Order spec.order spec.order Yes integer 0 No Tie-breaking priority when multiple listeners match
Ports spec.ports spec.ports No list of string — integers only, 1-65535 (no "8000-8010" range form) — No Ports the listener accepts connections on. At least one required. Port 22 is reserved for the Loadbalancer VM's own SSH access and is rejected. Each port must be unique across every listener (of any protocol) on the same Load Balancer
Hosts spec.hosts spec.hosts No list of string — hostname, optionally with a single leading *. wildcard, or a ~/~*-prefixed regex — No Host-header filter. At least one host is required; each entry is either a hostname (optionally a single leading *. wildcard, then standard DNS labels), or an nginx-style server_name regex — ~ (case-sensitive) / ~* (case-insensitive) followed by a regular expression, e.g. ~^(a|b)\.example\.com$
Security rules spec.securityRules spec.security_rules Yes list of rule objects [] No IP allow/deny list applied before routing
Order spec.securityRules[].order order Yes integer — No Evaluation order of the rule within this listener's allow/deny list — rules are checked in ascending order and the first one whose IPv4/IPv6 blocks contain the client IP decides allow or deny; traffic matching no rule is denied by default
Description spec.securityRules[].description description Yes string (nullable) — No Free-form note on what the rule is for
Action spec.securityRules[].action action No string — allow / deny — No Whether to allow or deny the matched IPs
IPv4 blocks spec.securityRules[].ipV4Blocks ipv4_blocks Yes list of string — CIDR [] No IPv4 ranges the rule matches
IPv6 blocks spec.securityRules[].ipV6Blocks ipv6_blocks Yes list of string — CIDR [] No IPv6 ranges the rule matches. IPv6 is not yet implemented — this field is reserved for future use
Examples

An HTTP listener on port 80 of an existing load balancer.

Terraform

Python SDK

kc CLI


Related pages

Resource docs

Examples

More in this section

An unhandled error has occurred. Reload 🗙