Konnect entities: Key Set

[randmonkey]

Problem statement

Introduce KongKeySet. As introduced here https://docs.konghq.com/gateway/latest/reference/key-management/, a Key requires a KeySet which it belongs to.

Proposed solution

• Introduce KongKeySet CRD in https://github.com/Kong/kubernetes-configuration

  • All Kong configuration CRDs will live in that repository to prevent import cycles between KGO and KIC
  • This CRD will contain a ControlPlane reference. Only references that refer to Konnect will result in reconciliation against Konnect.

• Implement a reconciler which will use that CRD.

• This reconciler should be able to be disabled via CLI flag / env variable.

  • There should exist only 1 CLI flag / env variable for all Kong configuration entities like Consumers, Services, Routes etc.

Acceptance criteria

• KGO can create, delete and update KeySets in Konnect based on the CRD spec.
• Status fields of this CRD are filled with information such as
  • Indication whether the entity in Konnect has been created via a Programmed status condition