The latest articles on DEV Community by Deepak Rawte (@anxious_morty). https://dev.to/anxious_morty https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F491704%2F1f36b896-9b3e-468d-9588-7c7bd116a6be.jpg https://dev.to/anxious_morty en Deepak Rawte Sat, 07 Oct 2023 07:05:37 +0000 https://dev.to/anxious_morty/severity-high-security-problem-to-be-announced-with-curl-840-on-oct-11-2kk8 https://dev.to/anxious_morty/severity-high-security-problem-to-be-announced-with-curl-840-on-oct-11-2kk8 <p>Just like log4j, a potential issue incoming next week that might affect the curl.<br> Read more: <a href="https://github.com/curl/curl/discussions/12026">https://github.com/curl/curl/discussions/12026</a></p> curl log4j cve vulnerabilities Deepak Rawte Sat, 09 Sep 2023 18:14:25 +0000 https://dev.to/anxious_morty/incorrect-output-on-numcpu-when-using-cgroups2-8ad https://dev.to/anxious_morty/incorrect-output-on-numcpu-when-using-cgroups2-8ad <p>Assuming it as a helm-chart deployment*</p> <ul> <li><p>On a cgroup2 enabled k8s cluster, in ingress controller pod the nginx process will use all the cores of the node and will not be restricted by container resource limits. This can cause OOM and ingress-controller pod will go to a CrashLoopBackOff.</p></li> <li><p>As of now, workaround is to set the worker_processes in a configmap (nginx.conf).</p></li> </ul> <p>Ref: <a href="https://github.com/kubernetes/ingress-nginx/issues/9665">https://github.com/kubernetes/ingress-nginx/issues/9665</a></p> nginx ingressnginx