amazon-eks-ami VS Metasploit

Careful assuming system reserved will be present. Last I checked, AWS EKS does not have system reserved resources for the kubelet by default and as a result, pods can starve those for resources (e.g., https://github.com/awslabs/amazon-eks-ami/issues/79). This is of course more important for memory, but could impact CPU as well.

For example, this is available for AL2: https://github.com/awslabs/amazon-eks-ami

I found this document that lists the pod limits per node size. I suspect you will want to consider larger worker nodes or you will very quickly be unable to schedule additional workloads.

source

Issue 1 is a known issue due to memory reservation being to low, see e.g. https://github.com/awslabs/amazon-eks-ami/issues/1145

No, the new node is added if there are not enough resiurces to start a new pod. So if you have many pods with small resource usage you can hit the pod per node limit, on eks you have a max number of pods depending on the instance type - https://github.com/awslabs/amazon-eks-ami/blob/master/files/eni-max-pods.txt You can incerase that limit : https://docs.aws.amazon.com/eks/latest/userguide/cni-increase-ip-addresses.html

# of pods are essentially capped by the worker node choice.

below excerpt from: https://github.com/awslabs/amazon-eks-ami/blob/master/files/...

  # Mapping is calculated from AWS EC2 API using the following formula:

See also: EKS nodes lose readiness when containers exhaust memory

So it manifests itself in this way: your pod is scheduled but remains pending forever. You check the logs and you see that it's complaining that the an IP address. Ultimately, if you check here, you see the maximum number of pods that can be scheduled on any underlying ec2 instance, even if you have remaining IPs in your subnet. I found this to be one of the most poorly understood phenomena in EKS. Even those who claimed to "crack" it and wrote fancy blog posts about it fundamentally got it wrong. AFAIK this document reflects the official AWS guide on how to mitigate this.

Metasploit

Metasploit: https://github.com/rapid7/metasploit-framework

1-) Learn Hacking on a debian based distro like Kali Linux - I personally started with tools like nikto, camhacker... and then moved to more complex frameworks like metasploit.

I once had to give a presentation about Metasploit, and whether it was ethically correct for the creator to make it free and open-source, available to everyone. And in researching this I realized that there were a lot of parallels between the arguments for or against hacking tools being readily available and the arguments for or against gun control. I'll just list a few quickly:

Metasploit Framework (mentioned earlier)

This phase is where the pen testers practically prove that there exist potential vulnerabilities in the target system. The pen testers do the hacking using an array of technical approaches and social engineering methods to exploit the vulnerabilities. The ethical hackers commonly use Metasploit framework to automatically execute exploitation against the target systems. Moreover, they may install malwares such as rootkit to persistently maintain their foothold and further compromise the target system.