Konnect entities: Data Plane Client Certificates

[pmalek]

Problem statement

Introduce KongDataPlaneClientCertificate.

API details: https://kong-platform-api.netlify.app/konnect/control-planes-config/v2/openapi.yaml/#tag/DP-Certificates

Proposed solution

• Introduce KongDataPlaneClientCertificate 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 DataPlane's client certificates 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

[pmalek]

After chatting with @mlavacca we can take a look into this one if it makes sense to support this type in https://github.com/Kong/gateway-operator/blob/1b094236f29f0413d426b50dfb74456aff2db879/api/v1alpha1/dataplane_konnect_extension_types.go#L93-L95.

@mlavacca said he'll look into this.