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

Find Das Schiff traffic mirror configuration

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

Find the Das Schiff MirrorTarget and MirrorSelector resources the Sylva Collector and TrafficMirror replace, and report for each whether it moves automatically or why it has to be moved by hand. Reports only; nothing is rewritten.

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

1 parameters
1 optional
ParameterExampleTypeRequired
fileMatcher**/mirror-*.ymlStringOptional
Matching files will be searched. This is a glob expression.

Examples

yaml
ParameterValue
fileMatchernull
Before
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: VRFRouteConfiguration
metadata:
name: mirror-test-vrf
spec:
vrf: mirror
loopbacks:
- name: lo.mir
subnet: 10.250.91.0/29
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: MirrorTarget
metadata:
name: collector-prod
spec:
type: l3gre
destinationIP: 10.250.90.100
destinationVrf: mirror
sourceLoopback: lo.mir
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: MirrorSelector
metadata:
name: mirror-vrf-egress
spec:
mirrorTarget:
kind: MirrorTarget
name: collector-prod
mirrorSource:
kind: VRFRouteConfiguration
name: mirror-test-vrf
direction: egress
After
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: VRFRouteConfiguration
metadata:
name: mirror-test-vrf
spec:
vrf: mirror
loopbacks:
- name: lo.mir
subnet: 10.250.91.0/29
---
apiVersion: network.t-caas.telekom.com/v1alpha1
~~(becomes `Collector`)~~>kind: MirrorTarget
metadata:
name: collector-prod
spec:
type: l3gre
destinationIP: 10.250.90.100
destinationVrf: mirror
sourceLoopback: lo.mir
---
apiVersion: network.t-caas.telekom.com/v1alpha1
~~(mirrors `VRFRouteConfiguration` mirror-test-vrf, and `TrafficMirror.spec.source.kind` is one of `Layer2Attachment`, `Inbound` or `Outbound`, none of which is a whole VRF)~~>kind: MirrorSelector
metadata:
name: mirror-vrf-egress
spec:
mirrorTarget:
kind: MirrorTarget
name: collector-prod
mirrorSource:
kind: VRFRouteConfiguration
name: mirror-test-vrf
direction: egress

Usage

Run this recipe

This recipe has no required configuration options. Users of Moderne can run it via the Moderne CLI.

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

shell
mod run . --recipe FindMirrorConfig

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

Traffic mirror configurations
io.moderne.kubernetes.sylva.migrate.dasschiff.table.MirrorConfigs

Deutsche Telekom MirrorTarget and MirrorSelector resources that the network-connector.sylvaproject.org Collector and TrafficMirror replace, and whether each one can be moved mechanically.

ColumnDescription
Source pathThe path to the manifest.
KindThe legacy kind.
NameThe metadata.name of the legacy resource.
ReferenceThe VRF a MirrorTarget tunnels through, or the MirrorTarget a MirrorSelector sends to. Empty when it names none.
Migrationautomatic when io.moderne.kubernetes.sylva.migrate.dasschiff.MigrateMirrorConfigToIntent rewrites this resource, manual otherwise.
Intent kindsThe intent resource it becomes, empty when it has to be moved by hand.
DetailWhy the resource cannot be moved mechanically, empty when it can.
Manual follow-upWhat still has to be done by hand once the resource has moved, which is mostly the resources it names that the intent group has not generated yet. Empty when the move leaves nothing behind.
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.