## What this PR does Adds the `service.kubernetes.io/service-proxy-name: "cozy-proxy"` label to VM LoadBalancer services when `external: true`. This tells Cilium to completely ignore the service — no BPF entries, no DNAT, no wildcard drops. Routing continues to work through kube-ovn (`networking.cozystack.io/wholeIP` annotation) and MetalLB L2 advertisement is unaffected. **This fixes two issues:** 1. **Inter-tenant connectivity via public LB IPs**: With `kube-proxy-replacement: true`, Cilium DNATs traffic destined to LB IPs (on ports declared in the Service) to the backend pod IP *before* evaluating network policies. The `CiliumClusterwideNetworkPolicy` then sees a cross-tenant pod-to-pod flow and blocks it. Ports not in the Service pass as "world" traffic and work fine — so does ICMP. With this label, Cilium doesn't DNAT anything, all traffic is classified as "world", and the existing `allow-external-communication` policy allows it. Pod IP isolation between tenants is preserved. 2. **WholeIP broken on Cilium 1.19+** (#2327): Cilium 1.19 introduced wildcard service drop entries (`cilium/cilium#40684`) that drop all traffic to a LB IP on ports not declared in the Service, before it reaches netfilter/cozy-proxy. With this label, no BPF entries are created at all, so there's nothing to drop. **Tested on our lab cluster:** - Cilium 1.18.6: inter-tenant via LB IP ✅, pod IP blocked ✅, external SSH ✅, WholeIP all ports ✅ - Cilium 1.19.1: same results ✅, no wildcard drops ✅ - MetalLB L2 advertisement: unaffected ✅ - Other services without the label: unaffected ✅ **Note:** The `externalPorts` / PortList filtering is currently not enforced at the network level (the `wholeIP` annotation causes kube-ovn to route all ports regardless). This was the case before this change and is a separate concern — per-VM CiliumNetworkPolicies could be re-introduced for that (ref: `4cbf562a`, #1601). ```release-note [virtual-machine] Fix inter-tenant connectivity via public LB IPs and WholeIP on Cilium 1.19+ ```
Cozystack
Cozystack is a free PaaS 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 Feature Requests please use the Discussion's Feature Request section.
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.
