-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
None
-
4.13.z
-
None
-
Low
-
None
-
False
-
-
Description of problem:
Will Red Hat handle that alert in the future as silenced? or remove the alert because its not saying anything? Will Red Hat handle the default class to use the default ingress class if the customer is setting up this optional field?
Version-Release number of selected component (if applicable):
4.13.41
How reproducible:
Happens all the timed once upgraded to v.4.13.z
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Remove the alert because its not saying anything Handle the default class to use the default ingress class if the customer is setting up this optional field Silence alert by default
Additional info:
Customer informs that they see around 1000 warnings about IngressWithoutClass name in our cluster , they did patching but it remains same after some time so we need a permanent solution .