Timofei Larkin 522513f65c feat(metallb-iad): fence the driver-managed MetalLB annotations
A reservation is only as good as the annotations that express it. The
driver parks an address on a placeholder Service and hands it over by
pinning the workload's Service with metallb.io/loadBalancerIPs — ordinary
MetalLB annotations that any writer of a Service can set, so a tenant able
to set them can steer MetalLB at an address reserved for someone else. The
driver notices and marks the address Conflict, but only after the fact, and
during the handoff gap the address is briefly unheld in MetalLB's books
with admission the only thing in front of it.

The driver's design leaves this policy to the installation rather than the
controller, since who is allowed to pin is a property of the deployment;
this package is that installation, so the policy ships beside the chart it
protects and is withdrawn with it.

Presence of an annotation is deliberately not what is forbidden: the driver
writes the pin onto the tenant's own Service, and the tenant must stay able
to edit the rest of it. The comparison is against oldObject, so an
unchanged value always passes, while CREATE sees a null oldObject and reads
as absent. spec.loadBalancerIP needs no clause — MetalLB stopped honouring
it in v0.14 and this tree vendors v0.16.1.

Assisted-by: LLM
Signed-off-by: Timofei Larkin <lllamnyp@gmail.com>
2026-10-13 13:38:01 +02: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 46.8%
Shell 37.8%
TypeScript 7%
Go Template 5.5%
Makefile 1.5%
Other 1.2%