added rules to detect ingress nginx as it is being deprecated #71
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
pedrobpereira
previously approved these changes
Nov 13, 2025
pedrobpereira
approved these changes
Nov 18, 2025
|
While this detects the nginx ingress correctly, does it also make sense to search for the IngressClass for nginx as well? That way we would notify anyone with any remnant of the nginx setup. |
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.
https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/
k8s ingress nginx is being deprecated -- this is a key piece of k8s infrastructure that many, many people rely on and by March it will be retired. It will be a big job for many teams to update their ingress safely so if we can start flagging it now.