Description of problem: When the number of networks in the k8s project exceeds the quota the kuryr-controller pod restarts indefinitely. A pod can't be created in a namespace but a pod in the default namespace can. When networks are deleted so the number of networks is again within the quota limits the kuryr-controller pod stops restarting. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.As described in the description 2. 3. Actual results: Expected results: Additional info:
What would be your expected behavior?
IMO the correct behavior should be as follows: 1. Liveness probe shouldn't be failing. Service is up, though unhealthy. 2. Readiness probe should check the quotas and signal if we have 0 space left with any resource we need. My only concern is that it seems to be impossible to give any message through the healthcheck mechanism, which is suboptimal.
I think that Michal's comment should satisfy the requirement.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0944