Skip to main content

No topics are shown

Kadeck uses WebSockets for real-time updates in the Data Catalog and Data Browser. If both views show no topics or data (or keep showing loading indicators), the root cause is often that a reverse proxy or ingress controller does not allow WebSocket (HTTP Upgrade) connections.

Ingress configuration

Most ingress controllers and reverse proxies need explicit configuration to allow HTTP connection upgrades for WebSockets. If this is missing, the browser cannot establish a WebSocket connection and Kadeck cannot load topics or data.

To fix this, make sure that:

  • Your ingress / proxy uses HTTP/1.1 for upstream connections.
  • The Upgrade and Connection headers are forwarded unchanged.
  • Long‑lived connections are allowed (sufficient read / idle timeout).

For example, in an NGINX-based reverse proxy you need a configuration similar to:

location / {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}

For other ingress controllers (for example Kubernetes ingress, cloud load balancers, or API gateways), consult their documentation on enabling WebSocket / HTTP Upgrade support and ensure it is enabled for the Kadeck service.