feat: set warning status for deprecated fields #7797
Merged
Conversation
This file contains hidden or 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
rudrakhp
force-pushed
the
deprecated_status_warning
branch
from
56741e7 to
790bb0c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7797 +/- ##
==========================================
+ Coverage 72.72% 72.78% +0.06%
==========================================
Files 235 235
Lines 35100 35165 +65
==========================================
+ Hits 25526 25595 +69
+ Misses 7757 7754 -3
+ Partials 1817 1816 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
jukie
reviewed
Dec 23, 2025
rudrakhp
force-pushed
the
deprecated_status_warning
branch
from
790bb0c to
c91527d
Compare
Member
Author
|
@jukie thanks for pointing that out, I was in the middle of a refactor, didn't give it a good look. Can you review this now? |
rudrakhp
force-pushed
the
deprecated_status_warning
branch
6 times, most recently
from
4298f48 to
1b5902e
Compare
Contributor
|
/retest |
jukie
previously approved these changes
Dec 24, 2025
arkodg
reviewed
Dec 27, 2025
arkodg
reviewed
Dec 27, 2025
Contributor
|
thanks for picking this one up, this should make it much easier to get users on the recommeneded path, added minor comments |
rudrakhp
force-pushed
the
deprecated_status_warning
branch
from
1b5902e to
634bc2b
Compare
jukie
previously approved these changes
Dec 27, 2025
Signed-off-by: Rudrakh Panigrahi <rudrakh97@gmail.com>
rudrakhp
force-pushed
the
deprecated_status_warning
branch
from
9c4f79f to
e9ea3b8
Compare
Signed-off-by: Arko Dasgupta <arkodg@users.noreply.github.com>
arkodg
approved these changes
Jan 2, 2026
millermatt
pushed a commit
to millermatt/envoy-gateway
that referenced
this pull request
Jan 4, 2026
Signed-off-by: Rudrakh Panigrahi <rudrakh97@gmail.com> Signed-off-by: Arko Dasgupta <arkodg@users.noreply.github.com> Co-authored-by: Arko Dasgupta <arkodg@users.noreply.github.com> Signed-off-by: Matt Miller <millermatt@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 type of PR is this?
feat: set warning status for deprecated fields
What this PR does / why we need it:
Introduces a warning status condition for xPolicy resources if deprecated fields are used. This will be helpful in highlighting usage of these deprecated fields and can also be used for other such issues that need to be highlighted by EG.
Which issue(s) this PR fixes:
Related #6717
Release Notes: Yes