Skip to main content
Moderne OnlyThis recipe is proprietary to Moderne and runs on the Moderne platform or CLI — it isn’t part of the open-source catalog. Available with a Moderne subscription.Contact Sales

Generate Inbound and Outbound from export ranges

Recipe IDio.moderne.kubernetes.sylva.migrate.dasschiff.GenerateInboundAndOutboundFromExportRanges
Artifactorg.openrewrite.recipe:rewrite-kubernetes

Generate a Sylva Inbound or Outbound for each VRFRouteConfiguration.spec.export range the classifications option names as a load balancer pool or an egress NAT pool. Nothing in the legacy group tells the two apart, so an unclassified range is reported and left alone rather than guessed at.

Single recipeOpenRewriteModerne Proprietary License
Try in PlatformTry this recipe in the Moderne platform. Not a user yet? You’ll get a no-setup demo environment, with nothing to install or configure.

Options​

2 parameters
1 required1 optional
ParameterExampleTypeRequired
classificationsm2m/10.250.4.0/24=inbound-bgp:vlan1,m2m/10.250.2.0/30=outbound:vlan1StringRequired
What each exported range is for, as <vrf>/<cidr>=<role>:<networkRef> separated by commas. The roles are inbound-bgp, inbound-l2 and outbound.
fileMatcher**/network-*.ymlStringOptional
Matching files will be modified. This is a glob expression.

Examples​

yaml
ParameterValue
classificationsM2M
fileMatchernull
Before
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: VRFRouteConfiguration
metadata:
  name: m2m-test-vrf
spec:
  export:
  # VLAN 1
  - cidr: 10.250.0.0/24
    le: 32
    action: permit
  - cidr: fd94:685b:30cf:501::/64
    le: 128
    action: permit
  # VLAN 2
  - cidr: 10.250.1.0/24
    le: 32
    action: permit
  - cidr: fd94:685b:30cf:502::/64
    le: 128
    action: permit
  # egress nat
  - cidr: 10.250.2.0/30
    le: 32
    action: permit
  - cidr: fd90:4dbf:396d::/126
    le: 128
    action: permit
  # bgpaas
  - cidr: 10.250.3.0/24
    le: 32
    action: permit
  - cidr: fd75:2d70:f7f7::/64
    le: 128
    action: permit
  # ingress
  - cidr: 10.250.4.0/24
    le: 32
    action: permit
  - cidr: fdbb:6b17:90ba::/64
    le: 128
    action: permit
  import: []
  seq: 10
  vrf: m2m
  vni: 2002026
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: Layer2NetworkConfiguration
metadata:
  name: vlan1
spec:
  anycastGateways:
  - 10.250.0.1/24
  id: 501
  vni: 4000002
  vrf: m2m
After
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: VRFRouteConfiguration
metadata:
  name: m2m-test-vrf
spec:
  export:
  # VLAN 1
  - cidr: 10.250.0.0/24
    le: 32
    action: permit
  - cidr: fd94:685b:30cf:501::/64
    le: 128
    action: permit
  # VLAN 2
  - cidr: 10.250.1.0/24
    le: 32
    action: permit
  - cidr: fd94:685b:30cf:502::/64
    le: 128
    action: permit
  # egress nat
  - cidr: 10.250.2.0/30
    le: 32
    action: permit
  - cidr: fd90:4dbf:396d::/126
    le: 128
    action: permit
  # bgpaas
  - cidr: 10.250.3.0/24
    le: 32
    action: permit
  - cidr: fd75:2d70:f7f7::/64
    le: 128
    action: permit
  # ingress
  - cidr: 10.250.4.0/24
    le: 32
    action: permit
  - cidr: fdbb:6b17:90ba::/64
    le: 128
    action: permit
  import: []
  seq: 10
  vrf: m2m
  vni: 2002026
---
apiVersion: network-connector.sylvaproject.org/v1alpha1
kind: Outbound
metadata:
  name: m2m-test-vrf-outbound-vlan1
spec:
  networkRef: "vlan1"
  destinations:
    matchLabels:
      network-connector.sylvaproject.org/vrf: "m2m"
  addresses:
    ipv4:
      - 10.250.2.0/30
    ipv6:
      - fd90:4dbf:396d::/126
---
apiVersion: network-connector.sylvaproject.org/v1alpha1
kind: Inbound
metadata:
  name: m2m-test-vrf-inbound-bgp-vlan1
spec:
  networkRef: "vlan1"
  destinations:
    matchLabels:
      network-connector.sylvaproject.org/vrf: "m2m"
  addresses:
    ipv4:
      - 10.250.4.0/24
    ipv6:
      - fdbb:6b17:90ba::/64
  advertisement:
    type: bgp
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: Layer2NetworkConfiguration
metadata:
  name: vlan1
spec:
  anycastGateways:
  - 10.250.0.1/24
  id: 501
  vni: 4000002
  vrf: m2m

Usage​

Run this recipe

You will need to have configured the Moderne CLI on your machine before you can run the following command.

shell
mod run . --recipe GenerateInboundAndOutboundFromExportRanges --recipe-option "classifications=m2m/10.250.4.0/24=inbound-bgp:vlan1,m2m/10.250.2.0/30=outbound:vlan1" --recipe-option "fileMatcher='**/network-*.yml'"

If the recipe is not available locally, then you can install it using:

RELEASE resolves to the newest release and LATEST to the newest build of any kind, including snapshots. Either one lets mod config recipes upgrade pull in later versions without editing this command; a pinned version stays where you put it.

mod config recipes jar install org.openrewrite.recipe:rewrite-kubernetes:RELEASE

Data tables​

Exported ranges
io.moderne.kubernetes.sylva.migrate.dasschiff.table.ExportRanges

Every spec.export range of a Deutsche Telekom VRFRouteConfiguration, and whether it is classified as the load balancer pool or the egress NAT pool the network-connector.sylvaproject.org intent group needs it to be.

ColumnDescription
Source pathThe path to the manifest.
NameThe metadata.name of the VRFRouteConfiguration exporting the range.
VRFThe VRF the range is exported into.
CIDRThe exported range.
Classification keyThe key that classifies this range, to be supplied as <key>=<role>:<networkRef>. Empty when no classification would help.
Statusgenerated when an Inbound or Outbound was produced, unclassified when the range needs a role, not expressible when no intent resource can hold it, and templated when the resource renders through a Helm expression.
RoleThe supplied role: inbound-bgp, inbound-l2 or outbound. Empty when unclassified.
NetworkThe Network the supplied classification allocates from. Empty when unclassified.
GeneratedThe intent resource this range landed in, empty when none was generated.
DetailWhat has to be decided, why the range cannot move, or what generating it adds beyond the export the legacy resource performed.
Source files that had results
org.openrewrite.table.SourcesFileResults

Source files that were modified by the recipe run.

ColumnDescription
Source path before the runThe source path of the file before the run. null when a source file was created during the run.
Source path after the runA recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Parent of the recipe that made changesIn a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all.
Recipe that made changesThe specific recipe that made a change.
Estimated time savingAn estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds.
CycleThe recipe cycle in which the change was made.
Source files that had search results
org.openrewrite.table.SearchResults

Search results that were found during the recipe run.

ColumnDescription
Source path of search result before the runThe source path of the file with the search result markers present.
Source path of search result after run the runA recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
ResultThe trimmed printed tree of the LST element that the marker is attached to.
DescriptionThe content of the description of the marker.
Recipe that added the search markerThe specific recipe that added the Search marker.
Source files that errored on a recipe
org.openrewrite.table.SourcesFileErrors

The details of all errors produced by a recipe run.

ColumnDescription
Source pathThe file that failed to parse.
Recipe that made changesThe specific recipe that made a change.
Stack traceThe stack trace of the failure.
Recipe performance
org.openrewrite.table.RecipeRunStats

Statistics used in analyzing the performance of recipes.

ColumnDescription
The recipeThe recipe whose stats are being measured both individually and cumulatively.
Source file countThe number of source files the recipe ran over.
Source file changed countThe number of source files which were changed in the recipe run. Includes files created, deleted, and edited.
Cumulative scanning time (ns)The total time spent across the scanning phase of this recipe.
Max scanning time (ns)The max time scanning any one source file.
Cumulative edit time (ns)The total time spent across the editing phase of this recipe.
Max edit time (ns)The max time editing any one source file.