Add new upstream fields #2822
Merged
Add new upstream fields #2822
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
randmonkey
previously approved these changes
Aug 16, 2022
rainest
force-pushed
the
feat/upstream-update
branch
from
7e32ffb
to
923a1dc
Compare
rainest
removed
the
do not merge
rainest
force-pushed
the
feat/upstream-update
branch
from
923a1dc
to
1e6bdf4
Compare
|
Rebased to current main, which uses deck v1.14.0, and added changelog entry; should be all set. |
pmalek
approved these changes
Aug 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Adds new 3.x upstream fields to KongIngress.
Which issue this PR fixes:
Fix #2812
Special notes for your reviewer:
Depends on a new deck release that includes Kong/deck#735released in v1.14.0PR Readiness Checklist:
Complete these before marking the PR as
ready to review:CHANGELOG.mdrelease notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR