Migrate Das Schiff traffic mirror configuration to intent resources
io.moderne.kubernetes.sylva.migrate.dasschiff.MigrateMirrorConfigToIntentorg.openrewrite.recipe:rewrite-kubernetesOptions
Examples
yaml
| Parameter | Value |
|---|---|
| fileMatcher | null |
- yaml
- Diff
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: VRFRouteConfiguration
metadata:
name: mirror-test-vrf
spec:
vrf: mirror
vni: 2002099
routeTarget: "65188:2099"
loopbacks:
- name: lo.mir
subnet: 10.250.91.0/29
- name: lo.mir6
subnet: "fd94:685b:30cf:591::/125"
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: MirrorTarget
metadata:
name: collector-prod
spec:
type: l3gre
destinationIP: 10.250.90.100
key: 1001
destinationVrf: mirror
sourceLoopback: lo.mir
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: MirrorSelector
metadata:
name: mirror-vlan590-ingress
spec:
trafficMatch:
protocol: icmp
mirrorTarget:
apiGroup: network.t-caas.telekom.com
kind: MirrorTarget
name: collector-prod
mirrorSource:
apiGroup: network.t-caas.telekom.com
kind: Layer2NetworkConfiguration
name: vlan590
direction: ingress
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: VRFRouteConfiguration
metadata:
name: mirror-test-vrf
spec:
vrf: mirror
vni: 2002099
routeTarget: "65188:2099"
loopbacks:
- name: lo.mir
subnet: 10.250.91.0/29
- name: lo.mir6
subnet: "fd94:685b:30cf:591::/125"
---
apiVersion: network-connector.sylvaproject.org/v1alpha1
kind: Collector
metadata:
name: collector-prod
spec:
address: "10.250.90.100"
protocol: l3gre
key: 1001
mirrorVRF:
name: "mirror-test-vrf"
loopback:
name: "lo.mir"
subnet: "10.250.91.0/29"
---
apiVersion: network-connector.sylvaproject.org/v1alpha1
kind: TrafficMirror
metadata:
name: mirror-vlan590-ingress
spec:
source:
kind: Layer2Attachment
name: "vlan590"
collector: "collector-prod"
direction: ingress
trafficMatch:
protocol: ICMP
@@ -15,2 +15,2 @@
subnet: "fd94:685b:30cf:591::/125"
---
-apiVersion: network.t-caas.telekom.com/v1alpha1
-kind: MirrorTarget
+apiVersion: network-connector.sylvaproject.org/v1alpha1
+kind: Collector
metadata:
@@ -20,2 +20,2 @@
name: collector-prod
spec:
- type: l3gre
- destinationIP: 10.250.90.100
+ address: "10.250.90.100"
+ protocol: l3gre
key: 1001
@@ -23,2 +23,5 @@
destinationIP: 10.250.90.100
key: 1001
- destinationVrf: mirror
- sourceLoopback: lo.mir
+ mirrorVRF:
+ name: "mirror-test-vrf"
+ loopback:
+ name: "lo.mir"
+ subnet: "10.250.91.0/29"
---
@@ -26,2 +29,2 @@
sourceLoopback: lo.mir
---
-apiVersion: network.t-caas.telekom.com/v1alpha1
-kind: MirrorSelector
+apiVersion: network-connector.sylvaproject.org/v1alpha1
+kind: TrafficMirror
metadata:
@@ -31,10 +34,4 @@
name: mirror-vlan590-ingress
spec:
- trafficMatch:
- protocol: icmp
- mirrorTarget:
- apiGroup: network.t-caas.telekom.com
- kind: MirrorTarget
- name: collector-prod
- mirrorSource:
- apiGroup: network.t-caas.telekom.com
- kind: Layer2NetworkConfiguration
- name: vlan590
+ source:
+ kind: Layer2Attachment
+ name: "vlan590"
+ collector: "collector-prod"
direction: ingress
@@ -42,0 +39,2 @@
name: vlan590
direction: ingress
+ trafficMatch:
+ protocol: ICMP
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.
mod run . --recipe MigrateMirrorConfigToIntent
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.
- RELEASE
- LATEST
- Pinned version
mod config recipes jar install org.openrewrite.recipe:rewrite-kubernetes:RELEASE
mod config recipes jar install org.openrewrite.recipe:rewrite-kubernetes:LATEST
mod config recipes jar install org.openrewrite.recipe:rewrite-kubernetes:3.18.0
Data tables
Traffic mirror configurations
io.moderne.kubernetes.sylva.migrate.dasschiff.table.MirrorConfigsDeutsche Telekom MirrorTarget and MirrorSelector resources that the network-connector.sylvaproject.org Collector and TrafficMirror replace, and whether each one can be moved mechanically.
| Column | Description |
|---|---|
| Source path | The path to the manifest. |
| Kind | The legacy kind. |
| Name | The metadata.name of the legacy resource. |
| Reference | The VRF a MirrorTarget tunnels through, or the MirrorTarget a MirrorSelector sends to. Empty when it names none. |
| Migration | automatic when io.moderne.kubernetes.sylva.migrate.dasschiff.MigrateMirrorConfigToIntent rewrites this resource, manual otherwise. |
| Intent kinds | The intent resource it becomes, empty when it has to be moved by hand. |
| Detail | Why the resource cannot be moved mechanically, empty when it can. |
| Manual follow-up | What 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.SourcesFileResultsSource files that were modified by the recipe run.
| Column | Description |
|---|---|
| Source path before the run | The source path of the file before the run. null when a source file was created during the run. |
| Source path after the run | A 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 changes | In 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 changes | The specific recipe that made a change. |
| Estimated time saving | An estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds. |
| Cycle | The recipe cycle in which the change was made. |
Source files that had search results
org.openrewrite.table.SearchResultsSearch results that were found during the recipe run.
| Column | Description |
|---|---|
| Source path of search result before the run | The source path of the file with the search result markers present. |
| Source path of search result after run the run | A recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run. |
| Result | The trimmed printed tree of the LST element that the marker is attached to. |
| Description | The content of the description of the marker. |
| Recipe that added the search marker | The specific recipe that added the Search marker. |
Source files that errored on a recipe
org.openrewrite.table.SourcesFileErrorsThe details of all errors produced by a recipe run.
| Column | Description |
|---|---|
| Source path | The file that failed to parse. |
| Recipe that made changes | The specific recipe that made a change. |
| Stack trace | The stack trace of the failure. |
Recipe performance
org.openrewrite.table.RecipeRunStatsStatistics used in analyzing the performance of recipes.
| Column | Description |
|---|---|
| The recipe | The recipe whose stats are being measured both individually and cumulatively. |
| Source file count | The number of source files the recipe ran over. |
| Source file changed count | The 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. |