Licenses - Kong Gateway | Kong Docs
Catalog row in Vendor License Sources · Cited
- Kind
- Product documentation
- Format
- HTML
- Applies to
- How a self-managed Kong Gateway Enterprise licence is deployed, loaded, expires and is reported. Undated documentation page, so the effective date is null.
- Evidence
- Enterprise licence file is issued with the subscription and checked at node start without network access
- Gateway checks licence sources in a fixed order at start-up
- Only the Admin API method propagates a licence from control plane to data planes
- An expired licence makes entities read-only but proxy traffic continues
- Licence reports are generated manually and are not sent to Kong