IvanHunters
28a59daa29
## What this PR does Removes the dead `serviceexposure` chainsaw suite and its wiring. Commit3dbc7d366dropped ExposureClass/ServiceExposure (api/network, the controller, and the `network.cozystack.io` CRDs shipped in `cozystack-controller/definitions`) in favor of the native LoadBalancer path, but the chainsaw port that landed the next day (dd2f89d20) brought the suite along, so it tests an API that no longer exists. Since then every full-suite E2E run — any PR touching core paths, and every release cut — fails `serviceexposure-delete` and `serviceexposure-externalips` with `no matches for network.cozystack.io/v1alpha1` (see the crust-gather snapshot of e.g. run 29561399440 on #3333: the network CRDs are absent while sibling CRDs from the same `definitions/` dir, like `tenantgateways.gateway.cozystack.io`, are present, confirming the chart applied and the API is simply gone). Alongside the suite dir this drops the `suite_to_source` case and its core-platform bats test in `hack/select-install*`, the now-unreachable `-` mapping mechanism itself (no suite returns it anymore and its only executable coverage was the removed bats test; re-adding the three lines with the next core-platform-owned suite is cheaper than keeping an untestable dead branch), and the suite list entry in `hack/e2e-chainsaw/README.md`. The `securitygroup` suite from the same port is alive and green and is untouched. If the native LoadBalancer replacement needs E2E coverage, that is a new suite against the new API, not a revival of this one. Verified: `hack/select-install.sh --validate` passes (97 sources), `select-install_test.bats` 17/17, `select-e2e_test.bats` 13/13. ## Release note ```release-note NONE ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Tightened installation suite-to-PackageSource validation: `serviceexposure` no longer has special handling, and mappings to `-` are now treated as invalid unless the referenced PackageSource exists. * **Tests** * Removed Chainsaw E2E fixture coverage and manifests for `serviceexposure`, and updated the listed E2E suites accordingly. * Updated installation mapping tests to match the stricter validation and added a negative validation case for a missing mapped PackageSource. * **Documentation** * Updated contributing guidance to reference the `networking.publishing.externalIPs` → `publishing.loadBalancerClass` migration. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.
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 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.