KongLicense
CRD
#5437
Labels
release/highlight
This part of the release is worth bragging about.
Milestone
KongLicense
CRD
#5437
Is there an existing issue for this?
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:
status
Additional information
No response
Acceptance Criteria
KongLicense
resourceThe text was updated successfully, but these errors were encountered: