The admission-webhook deny exempted any endpoint carrying k8s-app: konnectivity-agent, in any namespace. Because the rule disables default-deny, falling out of the deny is the entire access decision — so any pod anywhere could reach the webhook port by labelling itself, which is precisely the access the policy exists to remove. k8s-app is an ordinary pod label a workload sets on itself. Nothing in the platform constrains pod labels by admission, and Cilium keeps k8s-app identity-relevant (its label filter ships no default whitelist), so the forged label really does change the endpoint's identity rather than being filtered out. The namespace key is derived by Cilium from the pod's actual namespace and cannot be set by the workload. Splitting the deny in two keeps the carve-out and closes the hole: one selector for everything outside kube-system with no label condition at all, one for kube-system carrying the existing NotIn. Only the agent in its own namespace is exempt. Kamaji at the pinned 26.3.6-edge puts nothing but k8s-app: konnectivity-agent on the agent pod template (internal/resources/konnectivity/agent.go), so the label remains the only available discriminator and the namespace confinement is what makes it safe to key on. Tests cover both halves: the outside-kube-system selector must carry no label condition, and the kube-system selector must keep exactly the namespace and label pair. Reported-by: Daniil Myasnikov <myasnikovdaniil2001@gmail.com> Assisted-By: Claude Signed-off-by: Andrei Kvapil <andrei.kvapil@aenix.io>
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.
