Skip to content

feat(gateway): License expiration changes in 3.15#5458

Open
lena-larionova wants to merge 4 commits into
release/gateway-3.15from
feat/license-expiration
Open

feat(gateway): License expiration changes in 3.15#5458
lena-larionova wants to merge 4 commits into
release/gateway-3.15from
feat/license-expiration

Conversation

@lena-larionova
Copy link
Copy Markdown
Contributor

Description

Changes to unlicensed Gateway behavior in 3.15.

Fixes #5410

Preview Links

@lena-larionova lena-larionova requested a review from a team as a code owner June 4, 2026 06:52
Copilot AI review requested due to automatic review settings June 4, 2026 06:52
@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 4, 2026

Deploy Preview for kongdeveloper ready!

Name Link
🔨 Latest commit d593509
🔍 Latest deploy log https://app.netlify.com/projects/kongdeveloper/deploys/6a22f8965832de000889a8ed
😎 Deploy Preview https://deploy-preview-5458--kongdeveloper.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Kong Gateway documentation to describe changed behavior in 3.15 when a Gateway license expires (removal of legacy “free mode” behavior), by adding a 3.15 breaking-change entry and revising the License entity reference page.

Changes:

  • Added a new 3.15.x breaking changes section describing license-expiration impact.
  • Updated the License entity page’s FAQ formatting/capitalization and revised the “Expiration” behavior description.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File Description
app/gateway/breaking-changes.md Adds a 3.15.0.0 breaking change entry for license expiration behavior.
app/_gateway_entities/license.md Revises License entity reference content, especially the Expiration behavior section and related wording.

Comment thread app/gateway/breaking-changes.md Outdated
Comment thread app/gateway/breaking-changes.md Outdated
Comment thread app/_gateway_entities/license.md Outdated
Comment thread app/_gateway_entities/license.md
Comment thread app/_gateway_entities/license.md Outdated
Comment thread app/_gateway_entities/license.md Outdated
lena-larionova and others added 2 commits June 3, 2026 23:59
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

@juliamrch juliamrch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggested a few changes

Comment thread app/_gateway_entities/license.md Outdated
Comment thread app/gateway/breaking-changes.md Outdated
When a license expires, you can no longer change any {{site.base_gateway}} configuration.
The Admin API and all interfaces become read-only until a valid license is applied.

Existing configuration continues to be used, and all proxy traffic is processed normally.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Normally might be too vague, did you mean "as before the expiration"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, that is what I meant. I'll adjust.

Comment thread app/gateway/breaking-changes.md Outdated
Co-authored-by: Julia <101819212+juliamrch@users.noreply.github.com>
Co-authored-by: lena-larionova <54370747+lena-larionova@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants