Problem statement

Users might want to adopt already existing Konnect entities into their Kubernetes resources.

Currently (as implemented in #446), status.konnect.id drives the operator decision whether to create or update the Konnect entity. If that field is empty, the entity is created, otherwise its updated.

This task tracks the effort of introducing a mechanism which will allow users to adopt already existing entities.

Proposed solution

Implement a mechanism which will react to an annotation on Kubernetes resources mapping Konnect entities which will express user's intent to adopt the already existing entity.

This annotation's value would indicate which Konnect ID this resource is supposed to adopt.

konnect.konghq.com/adopt: c66a3c89-9bd4-4e2e-a6fa-1111111111111

Acceptance

• As a User I have means to create a Kubernetes resource and adopt already existing Konnect entity.

Sub-tasks

• Add konnect.entityID to allow adopting existing entities from Konnect kubernetes-configuration#232