search

GSA-TTS / datagov-brokerpak-eks

Broker AWS EKS instances using the OSBAPI (eg from cloud.gov)
Other
9 stars 7 forks source link

Use CIS hardened images #89

Closed nickumia-reisys closed 2 years ago

nickumia-reisys commented 2 years ago

Related to https://github.com/GSA/data.gov/issues/3668

nickumia-reisys commented 2 years ago

I suspect that the test failed because of this, image

It was trying to start the ebs-app and just hung there, so it would make sense..

nickumia-reisys commented 2 years ago

This is the best screenshot that I have for proof that the issue was with there not being enough nodes to run 2048 and ebs test workloads on, image

mogul commented 2 years ago

Could that have something to do with setting '--max-pods=20'? That would mean only 20 pods max would be scheduled on the single node, even if it had capacity to schedule more.

mogul commented 2 years ago

(I don't know what the default is when you don't specify that argument.)

nickumia-reisys commented 2 years ago

That could definitely have an effect! @mogul I could leave that option off. I guess I hadn't thought about that haha..

nickumia-reisys commented 2 years ago

(I don't know what the default is when you don't specify that argument.)

That's also true. I mean, we could specify a really high number and then let the CPU and Memory determine if a pod can run.

mogul commented 2 years ago

It looks like the default varies by instance type, and they're listed here.