Myasnikov Daniil e4a9d433ae docs(release): correct statements in the v1.7.0 changelog and release notes
A check against the code at v1.7.0-rc.3 and the upgrade-test records
found statements the evidence does not support. talos.registryMirrors
cannot be carried over from v1.6, which never had the key. Setting
version: v7.3 does not end the refusal of a release whose
cluster.version names 7.1. The lost migration log was one observation
on a test cluster, not a property of the chart, which keeps the Job.

The same check corrects narrower wording: the PostgreSQL restart was
seen from v1.6.5 only and v1.6.0 shipped CloudNativePG 1.28.1; a disk
added to spec.disks at v1.6.5 attaches only at the VM's next restart;
the controller waits on Kube-OVN only on the isp-full variants; host is
the node name; the API accepts a spec.cluster edit and the chart refuses
it; the copy clone strategy is a CDI setting; and CRD validation
ratcheting lets an unchanged dotted prefix through.

The OpenSearch entry gains what a test cluster showed about the stale
securityconfig-update Job of an instance created on v1.6.x: deleting it
makes the operator recreate it on the platform's cluster domain. It
stops short of a recovery, because whether the instance then finishes
initializing was not confirmed.

The release notes become the GitHub release body, so the three of
these they repeat are corrected there too.

Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
2026-10-27 20:14:27 +00:00
2026-10-27 09:35:01 +00:00
2025-10-08 09:43:34 +05:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

GitHub Release Apache-2.0 License Commit activity OpenSSF Best Practices OpenSSF Scorecard CLOMonitor Support

Cozystack

Cozystack is a free and open-source platform and framework for building clouds.

Cozystack is a CNCF Sandbox 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.

Cozystack user interface

Use-Cases

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 are welcome to take on the fix yourself. Commits are used to generate the changelog, and their author will be referenced in it.

If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.

Community

You are welcome to join us in #cozystack, on either CNCF Slack (get an invite) or Kubernetes Slack (get an invite), in our Telegram group, and at our community meetings. Add them to your Google Calendar or iCal for convenience.

Project documents

Document What it covers
Governance How decisions are made and who makes them
Contributor Ladder How to grow from contributor to maintainer
Maintainers Who maintains the project
Code of Conduct What we expect of each other
Security Policy Reporting a vulnerability, and which releases get fixes
Adopters Who runs Cozystack in production
Roadmap Where the project is going

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.

Languages
Go 48.2%
Shell 36.9%
TypeScript 6.9%
Go Template 5.3%
Makefile 1.4%
Other 1.1%