From 85f055a976fca070de3dfd2f7faccafbccfa1609 Mon Sep 17 00:00:00 2001 From: Kajol Asabe Date: Thu, 7 Mar 2024 16:24:10 +0530 Subject: [PATCH] Update network concept doc with network peering --- docs/concepts/network-lifecycle.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/concepts/network-lifecycle.md b/docs/concepts/network-lifecycle.md index d44e3717..787f9f04 100644 --- a/docs/concepts/network-lifecycle.md +++ b/docs/concepts/network-lifecycle.md @@ -24,3 +24,20 @@ The valid `NetworkID` range can be configured using the `apiserver`s When deleting a `Network`, the corresponding `NetworkID` is cleaned up alongside the claiming `Network`. + +## Network Peering + +When creating network peering both `ironcore` `Network`s has to specify matching, +`spec.peerings` referencing each other respectively. A `ironcore` `Network` can be peered with +multiple `network`s in any namespcae. + +Once specified `apinetlet` `NetworkPeeringController` validates if all the specified `network`s are in +`Available` state,they do exists and have matching `peerings`. + +If validation is successful, `apinetlet` `NetworkPeeringController` updates `ironcore` `Network` +`status.peerings` with network peering `name`s and `spec.incomingPeerings` with valid +incoming peerings. Also `apinetlet` `NetworkPeeringController` updates `ironcore-net` `Network` +`spec.peeredIDs` with valid peered network's `providerID`'s. + +Once `ironcore-net` `Network` is updated with `spec.peeredIDs`, `metalnetlet` `NetworkController` +updates `metalnet` `Network` `spec.peeredIDs` with corresponding `ironcore-net` `Network` `spec.peeredIDs` \ No newline at end of file