Upgrading from KIC 2.9 to nightly (effectively 2.10 RC) breaks Konnect sync

[czeslavo]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

When a customer has an existing KIC Runtime Group with any Services, Routes, or Customers configured, upgrading from KIC 2.9 to 2.10 RC breaks synchronization of config to Konnect. It happens because of the fact that from 2.10 KIC started to assign those entities stable IDs, and when it tries to synchronize with Konnect (which still holds the old entities with their randomly assigned IDs yet the same names), it fails due to breaking the entities' unique name constraints.

This happens for deck synchronization, so not only Konnect RG might be affected, but also regular DB-mode setups.

The aim of this issue is to find a way to prevent such breakage and implement the proposed fix.

Proposed Solution

Find a way to fix the described problem and implement it.

Additional information

No response

Acceptance Criteria

• When upgrading KIC from 2.9 to 2.10 for a Konnect RG or a regular DB-mode setup with existing Services, Routes, or Consumers, the configuration can be synchronised without problems

[czeslavo]

It's confirmed that this bug affects regular DB-mode setups as well as Konnect.