Find Das Schiff resources that have to move to Sylva

Proprietary

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.

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

Install it once from Recipe actions, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.

Recipe list

It runs these recipes, in this order.

  1. Find legacy T-CaaS network resources
  2. Find VRFRouteConfiguration and Layer2NetworkConfiguration to migrate
  3. Find Das Schiff traffic mirror configuration
  4. Find what blocks a Das Schiff BGPPeering from moving to the Sylva network connector API
  5. Find drift between Das Schiff and Sylva intent network resources
  6. Find unclassified Das Schiff export ranges
  7. Find Das Schiff network operator ConfigMaps