Pod is internet facing (via ELB) and does not have CPU/MEM limits

Security & Compliance
No items found.

When a Pod is deployed as a service and is exposed to the internet via Elastic Load Balancer (ELB), it is important to ensure that the Pod has configured CPU/Memory limits. Without these limits, the Pod can consume all available resources on the node it is running on, potentially causing performance issues or even crashes. It is also recommended to use resource requests to ensure that the Pod has enough resources available to function properly. This helps ensure the reliability and availability of the Pod to handle traffic from the internet.


To remediate the issue where a Pod is internet-facing via an ELB and does not have CPU/MEM limits set, you can follow the below steps:

  1. Log in to the Kubernetes cluster using kubectl.
  2. Use the kubectl describe command to identify the Pod that is internet-facing via the ELB and does not have CPU/MEM limits set.
  3. Update the Pod's deployment configuration file to include CPU/MEM limits for the container running in the Pod.
  4. Use the kubectl apply command to apply the updated deployment configuration file to the Kubernetes cluster.
  5. Monitor the Pod to ensure that it is running with the updated configuration and verify that the CPU/MEM limits are being enforced.

Note: It is important to ensure that the CPU/MEM limits set are appropriate for the application running in the container. Setting the limits too low may impact the performance of the application, while setting them too high may lead to resource contention and impact the performance of other Pods running in the same node.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.