The release of the free PaaS platform Cozystack 0.37, built on Kubernetes, is now available. The project aims to provide a ready platform for hosting providers and a framework for building private and public clouds. The platform is installed directly on servers and covers all aspects of preparing the infrastructure for managed services. Cozystack allows for the deployment and management of Kubernetes clusters, databases, and virtual machines. The platform's code is available on GitHub and is distributed under the Apache-2.0 license.
Talos Linux and Flux CD are used as the foundational technology stack. The images with the system, kernel, and necessary modules are pre-built and updated atomically, which eliminates the need for components like dkms and package managers, ensuring stable operation. A simple installation method is provided in an empty data center using PXE and the Debian-like talos-bootstrap installer. The platform allows deploying Kafka, FerretDB, PostgreSQL, Cilium, Grafana, Victoria Metrics, and other services with a single click.
The platform includes a free implementation of network infrastructure that is based on Kube-OVN and uses Cilium for organizing the service network, with MetalLB for announcing services externally. Storage is implemented on LINSTOR, which offers the use of ZFS as a base layer for storage and DRBD for replication. A pre-configured monitoring stack is based on VictoriaMetrics and Grafana. To launch of virtual machines KubeVirt technology is used, which allows for running traditional virtual machines directly in Kubernetes containers and already has all the necessary integrations with Cluster API for launching managed Kubernetes clusters within the 'bare-metal' Kubernetes cluster.
In the past month and a half, the project team has released new versions 0.36 and 0.37. Changes in these releases include:
- The user interface has been completely rewritten. The openapi-ui project serves as the foundation.
- The interface now features a cluster selector. Currently, the dashboard operates in single-cluster mode (one dashboard per cluster). In the future, this same interface will be used for multi-cluster mode.
- The cluster screen now immediately displays all available tenant namespaces. The list is formed through the Kubernetes aggregation layer (tenant namespace), so only those namespaces with access are shown.
- Resource creation now occurs through forms automatically generated from the Kubernetes OpenAPI. Comments from YAML are not needed: fields and validation are drawn directly from the specifications.
- The specification for new applications is generated from Helm charts using the cozy-values generator, and the fields entered in the form are synchronously reflected in the final YAML.
- Tenant management modules have moved to the administration section: here you can create sub-tenants and assign specific modules/applications to them (access depends on the user's role and rights).
- The addition of a tab with a VNC console for virtual machines is planned. Specialized tabs/fields will be added for certain resource types (for example, for KubeVirt VMs).
- The resource management mechanism for Cozystack tenants has been stabilized. Platform administrators can now set explicit limits on CPU, memory, and storage for each tenant namespace in the tenant specification. This ensures that no tenant can "consume" all resources, leaving other tenants without resources.
- The Kube-OVN Plunger component has been added for continuous monitoring of the central control cluster status of the Kube-OVN network. An external agent collects the OVN cluster status and consensus information, displays Prometheus metrics, and streams events via SSE (Server-Sent Events).
- The CoreDNS add-on is now deployed via a Helm chart and configured in the cluster specification (auto-scaling, number of replicas, service IP, etc.). CoreDNS can be configured both in the dashboard and through the Cozystack API.
- S3 storage based on SeaweedFS has become more flexible at the component level. The Helm chart allows for independent configuration of each component and its resources: master nodes, volume servers (with support for multiple zones), database, and S3 gateway. Administrators can set the number of replicas, CPU/memory limits, and storage volume for each component.
- SeaweedFS 3.97 has been integrated with support for server-side encryption of S3 buckets (SSE-C, SSE-KMS, SSE-S3). When updating Cozystack, the SeaweedFS version will be updated, and the service specifications will be automatically converted to the new format.
- The NGINX controller is now configurable at the level of each replica: you can set requests/limits for CPU and memory directly or choose one of the predefined presets.
- If a virtual machine is assigned a public IP, it is always used for egress traffic, regardless of the method of assigning that IP.
Source: opennet.ru
