Andrei Kvapil
0faab1fa98
## What this PR does Replace DaemonSet-based deployment of cozystack-api with a regular Deployment using Service `trafficDistribution: PreferClose`. Previously, cozystack-api ran as a DaemonSet on control-plane nodes with `internalTrafficPolicy: Local` and direct host kube-apiserver access, providing strict node-local routing with no fallback. The new approach prefers routing to the nearest pod but gracefully falls back to remote pods when the local one is unavailable. Key changes: - Always deploy as Deployment instead of conditional DaemonSet/Deployment - Use `trafficDistribution: PreferClose` on the Service (matching seaweedfs pattern) - Remove `KUBERNETES_SERVICE_HOST`/`KUBERNETES_SERVICE_PORT` override - Replace hard `nodeSelector` with soft node affinity for control-plane nodes - Simplify the migration hook to always clean up leftover DaemonSet ### Release note ```release-note [platform] Switch cozystack-api from DaemonSet to Deployment with trafficDistribution: PreferClose for improved resilience ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Breaking Changes** * Removed localK8sAPIEndpoint configuration option; existing deployments relying on this setting require reconfiguration. * **Infrastructure Updates** * Simplified deployment resource strategy and updated service traffic distribution behavior to fixed configuration. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Cozystack
Cozystack is a free PaaS platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have Feature Requests please use the Discussion's Feature Request section.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.