← All recipes
Moderne licensed

Find Das Schiff resources that have to move to Sylva

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

Inventory every Das Schiff resource the Sylva intent group replaces and report, per kind, whether it moves automatically or what has to be decided first. All eight legacy kinds are marked, the three the operator generates included, so a kind that goes unmentioned is one this catalogue does not know about. A repository partway through the move also reports where the intent resources it already holds no longer say what the legacy ones do. Reports only; nothing is rewritten.

Composite recipekubernetestelekomProprietary

Usage

This recipe has no required configuration options. You’ll need the Moderne CLI configured before running the command below.

mod run . --recipe io.moderne.kubernetes.sylva.migrate.dasschiff.FindDasSchiffMigrationWork

If the recipe isn’t available locally, install it with:

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

Definition

This recipe runs the following recipes in order.

Data tables

Structured output this recipe can produce.

  • Low level network configurationsDeutsche Telekom `network.t-caas.telekom.com` resources that the `network-connector.sylvaproject.org` intent group replaces, and whether each one can be moved mechanically.io.moderne.kubernetes.sylva.migrate.dasschiff.table.LowLevelNetworkConfigs
  • Traffic mirror configurationsDeutsche Telekom `MirrorTarget` and `MirrorSelector` resources that the `network-connector.sylvaproject.org` `Collector` and `TrafficMirror` replace, and whether each one can be moved mechanically.io.moderne.kubernetes.sylva.migrate.dasschiff.table.MirrorConfigs
  • BGP peeringsDeutsche Telekom `network.t-caas.telekom.com` `BGPPeering` resources, and what each one needs decided before it can be written against the `network-connector.sylvaproject.org` `BGPPeering` that shares its name.io.moderne.kubernetes.sylva.migrate.dasschiff.table.BgpPeerings
  • Intent driftWhere the `network-connector.sylvaproject.org` resources in a repository do not say what the `network.t-caas.telekom.com` resources beside them said.io.moderne.kubernetes.sylva.migrate.dasschiff.table.IntentDrift
  • Exported rangesEvery `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.io.moderne.kubernetes.sylva.migrate.dasschiff.table.ExportRanges
  • Das Schiff network operator ConfigMapsOne row per `data` key of every `ConfigMap` that configures Deutsche Telekom's `das-schiff-network-operator`, describing where it lives and what shape it is in. A `ConfigMap` that declares no keys still gets a row, so that the inventory is of `ConfigMap`s and not only of keys.io.moderne.kubernetes.sylva.migrate.dasschiff.table.NetworkOperatorConfigMaps
  • Source files that had resultsSource files that were modified by the recipe run.org.openrewrite.table.SourcesFileResults
  • Source files that had search resultsSearch results that were found during the recipe run.org.openrewrite.table.SearchResults
  • Source files that errored on a recipeThe details of all errors produced by a recipe run.org.openrewrite.table.SourcesFileErrors
  • Recipe performanceStatistics used in analyzing the performance of recipes.org.openrewrite.table.RecipeRunStats