Aleksei Sviridkin 024a2d54c6 test(kubevirt): add a unit-test target for the operator package
hack/helm-unit-tests.sh discovers work by probing `make -C <dir> -n
test`, so a package with no such target is skipped in silence: the
whole per-package loop, including the guards that catch a suite which
asserts nothing, never reaches it. kubevirt-operator had no target and
no suite, so nothing rendered the package after a refresh and the sweep
stayed green reporting success.

The suite pins what the vendoring recipe is supposed to produce. The
local PrometheusRule has to still be there, addressed as a template so
helm-unittest fails outright if it goes missing. The operator
Deployment, selected by name rather than by index because the vendored
file is one long document stream, has to carry the pinned image and the
rewritten namespace, and no Namespace object may survive the second
transform. VIRT_OPERATOR_IMAGE and KUBEVIRT_VERSION are pinned beside
the image because the operator reads the latter to choose the tags for
virt-controller, virt-handler and virt-launcher: a manifest whose image
moved while those did not deploys a split control plane.

The Makefile check is the other half: helm-unittest reads the tree and
cannot see RELEASE, so bumping the pin without re-running `update`
would leave every assertion happily green against the old release.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-09-07 01:23:29 +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%