KongLicense CRD

[mflendrich]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

Following the pattern (of feeding the Kong license via Admin API) introduced in #3883 - we can expose the license API with a Kubernetes object.

Proposed Solution

Define a KongLicense CRD that will wrap the license string (similarly to how a k8s secret is used today).

Solve the outstanding problems:

• what to do if multiple license objects are present in the cluster (possibly some of them being expired) - for an initial version this can be a manual process
• ensure that if multiple KICs / ingress classes live in the cluster, they don't fight over the status
• define the priority of KongLicense versus the license obtained from Konnect (in case it's used)

Additional information

No response

Acceptance Criteria

• as an end-user I can control the licensed status of KIC-managed gateways by creating a KongLicense resource