Skip to content
kubestart

Ingress

kubestart provides a built-in ingress layer for routing external traffic to your services. For advanced routing needs, you can install an add-on ingress controller.

Built-in ingress

Section titled “Built-in ingress”

Every cluster includes the kubestart-ingress IngressClass. It routes traffic through the platform’s TLS-terminating load balancer to your services.

Use it for services that need HTTPS under your cluster’s *.{cluster-id}.kubestart.xyz domain or a custom domain.

Example: Expose a web app

Section titled “Example: Expose a web app”
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-app
spec:
  ingressClassName: kubestart-ingress
  rules:
    - host: app.abc123.kubestart.xyz
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: my-app
                port:
                  number: 80

The platform handles TLS termination automatically for the default *.kubestart.xyz domain. Your service only needs to serve plain HTTP.

What the built-in ingress supports

Section titled “What the built-in ingress supports”
  • HTTP and HTTPS routing by hostname and path
  • Automatic TLS for *.{cluster-id}.kubestart.xyz domains
  • Path-based routing (Prefix and Exact path types)

What it does not support

Section titled “What it does not support”
  • TCP/UDP routing (non-HTTP protocols)
  • Advanced traffic shaping (rate limiting, circuit breaking, retries)
  • Header-based routing or request transformation
  • Custom middleware or plugins

For these capabilities, install an add-on ingress controller.

Add-on ingress controllers

Section titled “Add-on ingress controllers”

For advanced routing needs, install one of the available ingress controller add-ons:

Add-onBest for
TraefikMiddleware chains, automatic HTTPS, Docker-native teams
NGINXBroad ecosystem support, familiar configuration
KongAPI gateway features, plugin ecosystem
HAProxyHigh-performance TCP/HTTP load balancing

Enable them from the add-ons page on the dashboard.

How add-on controllers work

Section titled “How add-on controllers work”

Add-on ingress controllers run inside your cluster as ClusterIP services. They receive traffic through the platform’s ingress layer — they do not get their own external IP or LoadBalancer.

To use an add-on controller, set ingressClassName to the controller’s class name (e.g., traefik, nginx) in your Ingress resources.

No LoadBalancer or NodePort

Section titled “No LoadBalancer or NodePort”

kubestart clusters do not support LoadBalancer or NodePort service types. All external traffic flows through the Ingress layer. See Networking for details.

Section titled “Related”