Fix max_pods to 110, set kubeReserved.memory using calculation scaling with max_pods and set systemReserved.memory to 200Mi

[wcarlsen]

Describe your changes

• kube_reserved_cpu (kubelet reserved CPU) since, this doesn't scale with max_pods. The scaling is calculated in this fashion (6% of the first core + 1% of the second core + 0.5% of the third and fourth core + 0.25% of the remainding cores.
• kube_memory (kubelet reserved memory) scales with Max Pods, but EKS doesn't handle overwrites to to Max Pods in terms of reserved memory. The calculation is as following 255Mi + (11Mi * Max_pods).
• Remove systemReserved.cpu since documentation say we should only set non-compressable resources see https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#general-guidelines
• Set systemReserved.memory to 200Mi since it is needed for the node not to go in NotReady state under stress testing. Kubernetes documentation has something on the topic https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#general-guidelines
• Added check block to throw a warning when instance types with lower than 110 max pods
• Fix max_pods to 110 always and remove variable

Here are the actual code setting some of these parameters:

• Memory https://github.com/awslabs/amazon-eks-ami/blob/d17a9d345efadc98bc0d9183391fe950a5b21ae6/nodeadm/internal/kubelet/config.go#L442-L443
• CPU https://github.com/awslabs/amazon-eks-ami/blob/d17a9d345efadc98bc0d9183391fe950a5b21ae6/nodeadm/internal/kubelet/config.go#L410

Issue ticket number and link

Checklist before requesting a review

• I have tested changes in my sandbox
• I have added the needed changes in the test/integration folder to apply my changes in QA. Read the guide on adding environment variables in QA
• I have rebased the code to master (or merged in the latest from master)

Is it a new release?

• Apply a release tag release:(major|minor|patch), following semantic versioning in this guide or norelease if there is no changes to the Terraform code

[DFDS-Snyk]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.