Open jayantapaul-18 opened 1 year ago
Hey. I think that the best way to "fix the error" in this case might be to specify the resource requirements of the init containers.
If not, please let me know why that's not a good solution for you.
Hey, thanks for quick response and recommendation . Let me try the resources cpu & memory for init-container and see if that resolve the alert or not.
I'm using init-containers with main containers and kube-score is throwing [CRITICAL] Container Resources alert . So, looking for a way to either fixed the warning or, way to ignored those warning just for init-containers .