Aleksei Sviridkin cdd78a249a fix(kubevirt): verify the operator manifest digest before vendoring
`make update` fetched the upstream release manifest straight over
templates/kubevirt-operator.yaml and applied its two transforms to
whatever arrived. A truncated download or an asset re-cut under an
existing tag both landed in the tree looking like a normal refresh, and
the only reviewer was whoever read the resulting diff. A wget that
failed outright was worse: `-O` had already emptied the vendored file
by then.

The fetch now happens outside templates/, is checked against
MANIFEST_SHA256, is transformed there, and only then moves in. So the
vendored file is written exactly once per refresh, with finished
content, and a failure at any step leaves it untouched. Keeping the
work out of templates/ matters because Helm renders every file in that
directory, and the directory also holds prometheusrule.yaml, which is
ours rather than upstream's.

Upstream signs the source tarball and publishes no checksum for this
generated manifest, so the pin is measured on download rather than
fetched alongside one. That makes it a detector for an asset moving
under its tag, not authenticity verification, and the comment says so.

RELEASE moves up to a make variable so the recipe and the pin sit
together. The digest command is resolved at parse time because
sha256sum is not universal: current macOS carries a native one, older
releases carry only shasum(1).

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-09-07 01:23:20 +03:00
2025-10-08 09:43:34 +05:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

Open Source Apache-2.0 License Support Active GitHub Release GitHub Commit OpenSSF Best Practices OpenSSF Scorecard

Cozystack

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

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 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 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 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.

Languages
Go 52%
Shell 34%
TypeScript 6.8%
Go Template 4.7%
Makefile 1.3%
Other 1.1%