Skip to content

Enhance Network Peering translation in apinetlet and metalnetlet with Peering Prefix #305

@kasabe28

Description

@kasabe28

Summary

Enhance network peering by exposing only specified Prefixes of peered network. Prefixes is a list of CIDRs that we want only to be exposed to the peered network, if no prefixes are specified no filtering will be done and entire network will be peered.

There will be no change in metalnet Network structure as Prefixes are already there. Only translation logic will be added in metalnetlet.

Apinet network structure along with prefixes will look like below:

Basic example

apiVersion: core.apinet.ironcore.dev/v1alpha1
kind: Network
metadata:
  namespace: apinetlet-system
  name: 2020dcf9-e030-427e-b0fc-4fec2016e73a
spec:
  id: "10606139"
  peerings:
    id: "19837404"
    name: "peering1"
    prefixes:
    - name: prefix1
      prefix: 10.30.0.0/24
status:
  peerings:
    id: "19837404"
    state: ready
---
apiVersion: core.apinet.ironcore.dev/v1alpha1
kind: Network
metadata:
  namespace: apinetlet-system
  name: 3030dcf9-f031-801b-f0f0-4fec2016e73a
spec:
  id: "19837404"
  peerings:
    id: "10606139"
    name: "peering1"
    prefixes:
    - name: prefix1
      prefix: 10.40.0.0/24
status:
  peerings:
    id: "10606139"
    state: ready

Metadata

Metadata

Assignees

Labels

area/networkingNetworking-related tasks and improvements.enhancementNew feature or request

Type

No type

Projects

Status

✅ Done

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions