Migrate T-CaaS network resources to the Sylva network connector API

Proprietary

Move what can be moved without a decision from Das Schiff's low level network.t-caas.telekom.com group onto the network-connector.sylvaproject.org intent group. Four of the eight legacy kinds move: VRFRouteConfiguration and Layer2NetworkConfiguration together rather than one at a time, because a VRF whose attachment stays behind stops advertising that attachment's subnet, and MirrorTarget and MirrorSelector likewise, because a selector without its collector points at nothing. BGPPeering is report-only. NodeNetworkConfig, NodeNetplanConfig and NetworkConfigRevision are operator output rather than input — the first two are named after a node and owned by it, the third by a hash of its own spec — so their absence is not a gap.

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

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. Migrate VRFRouteConfiguration community to communities
  2. Migrate VRFRouteConfiguration and Layer2NetworkConfiguration to Sylva
  3. Migrate Das Schiff traffic mirror configuration to intent resources