Cozystack 1.4, a free release of the PaaS-platform built on Kubernetes, is now available for hosting providers and developers building private and public clouds. The platform is designed to streamline infrastructure preparation for managed services and includes features such as Kubernetes cluster provisioning, database management, and virtual machine deployment. Cozystack’s code is open source and distributed under the Apache-2.0 license, available on GitHub.
Key components of Cozystack 1.4 include a network infrastructure based on Kube-OVN, service network organization with Cilium, and service announcement using MetalLB. Storage is managed through LINSTOR, utilizing ZFS for storage base layer and DRBD for replication. The platform also features a monitoring stack based on VictoriaMetrics and Grafana. KubeVirt technology is used to launch virtual machines within Kubernetes containers, with integrations for managing Kubernetes clusters. Users can easily deploy various services like Kafka, FerretDB, PostgreSQL, Cilium, Grafana, and Victoria Metrics within the platform.
Notable innovations in Cozystack 1.4.0 include a new management interface based on cozystack-ui, replacing the old openapi-ui and BFF stack with a React 19 and TypeScript interface. Persistent storage for worker nodes of tenant clusters has been implemented using PVC disks via KubeVirt dataVolumeTemplates. Additionally, a new resource presets scheme has been introduced to enhance resource management within the platform.
- Introduced a new management interface based on the project cozystack-ui. The old openapi-ui and BFF stack has been replaced with a front-end based on React 19 and TypeScript, which works directly with the Kubernetes API. In addition, the interface now includes support for dynamic VNC WebSocket URLs for virtual machines, runtime branding via ConfigMap, reading ApplicationDefinition for the application directory and redirecting old addresses /openapi-ui/*.
- Persistent storage has been implemented for worker nodes of tenant clusters. Worker virtual machines now use PVC disks via KubeVirt dataVolumeTemplates instead of emptyDisk. This ensures that kubelet certificates, kubeconfig, and containerd state are preserved after the virtual machine is restarted. The ephemeralStorage field has been renamed to diskSize, and a storageClass setting has been added at the NodeGroup level. During the migration process, old values are automatically converted.
- A new resource presets scheme