ignore incorrectly configured Ingresses when building IngressGroup #1676
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.
Ignore incorrectly configured Ingresses when building IngressGroup member list.
e.g.
my-xx#/eWhy would we want such change?
Test done
change one Ingress(within IngressGroup) to have invalid groupName(
my-group-2#)failed load groupID due to invalid ingress group: groupName must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric characterchange one Ingress(within IngressGroup) to have non-exists IngressClass
failed load groupID due to invalid ingress class: IngressClass.networking.k8s.io "my-class-2" not found