2c0a9fb2cc
Implement bilateral VPC peering using Kube-OVN's native vpcPeerings mechanism. Each VPC can declare peers by specifying the remote VPC name and tenant namespace. Peering is only activated by Kube-OVN when both sides declare each other, ensuring mutual consent. Key features: - Deterministic remote VPC ID resolution via sha256 hash - Auto-allocated link-local peering IPs (169.254.0.0/16) derived from sorted pair hash, eliminating manual IP coordination - Static routes support for fine-grained inter-VPC routing - ConfigMap enrichment with peer discovery info - Schema validation enforcing tenant- namespace prefix pattern Signed-off-by: Mattia Eleuteri <mattia.eleuteri@hidora.io> Signed-off-by: mattia-eleuteri <mattia@hidora.io> |
||
|---|---|---|
| .. | ||
| cozyrds | ||
| templates | ||
| Chart.yaml | ||
| Makefile | ||
| values.yaml | ||