Konnect entities: KongUpstream

[pmalek]

Problem statement

Introduce KongUpstream.

Proposed solution

• Introduce KongUpstream 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

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

[pmalek]

CRD in k-cfg: https://github.com/Kong/kubernetes-configuration/pull/65