Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: wording ON CHANGELOG for limiting gateway discovery to be used with dbless gateways #3653

Merged
merged 1 commit into from
Mar 3, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,8 +110,7 @@ Adding a new version? You'll need three changes:
- Added Gateway discovery using Kong Admin API service configured via `--kong-admin-svc`
which accepts a namespaced name of a headless service which should have
Admin API endpoints exposed under a named port called `admin`. Gateway
discovery is only allowed to run with dbless kong gateways, because it is
unnecessary to run gateway discovery with DB-backed kong gateways
discovery is only allowed to run with dbless kong gateways.
[#3421](https://github.com/Kong/kubernetes-ingress-controller/pull/3421)
[#3642](https://github.com/Kong/kubernetes-ingress-controller/pull/3642)
- Added configurable port names for Gateway discovery through
Expand Down