Skip to content
Klyo Changelog

Install Klyo Gateway on Kubernetes without Helm

v1.20.0 feature medium impact
  • deployment

Every release now ships a pre-rendered, credential-free Kubernetes manifest. Clusters that do not permit Helm can install the gateway with kubectl apply -f — no Helm CLI on the path. Defaults target a single-node production cluster: the web tier is exposed on NodePort 30300, so no ingress or load balancer is required. Operators create two secrets once (image pull and application credentials); upgrades are a re-apply with --prune.

Configuration is now persistent on Kubernetes. The config directory lives on a PersistentVolumeClaim seeded from the image, so runtime edits — the admin config editor, announcements, firewall rules — survive restarts and upgrades, matching Docker Compose. GitOps installs can mount a complete-config map instead.

No action required for managed tenants. Self-hosted operators can follow the Kubernetes install guide.