Steve Hipwell

@suket22 doesn't #855 cover most of the use case here (I know it's not perfect)? Basically additional kubelet args can be set but you can't override values explicitly set in...

@Skarlso the only specific arguments or env values are to override bootstrap.sh explicitly set kubelet args, which need to integrate with the bootstrap logic. In your desired design the full...

@Skarlso I don't think it's incomplete; if you're using bootstrap.sh you will need to provide variables to customise it's behaviour around the configuration it explicitly sets. For everything else you...

@Skarlso longer term I think a binary to process a well defined configuration is the way forward (as mentioned in #855). My personal vote goes for the Bottlerocket configuration (or...

@Skarlso it probably depends on the scope of the configuration supported, but it'd solve a number of hard problems. CC @bwagner5

@bwagner5 with a limited initial config scope and init container support all use cases would be catered for. As more of the Bottlerocket config is supported the fewer use cases...

@wh1sssss you have 3 different instance classes in your node group that might be causing you issues. I'd drop the t2 as it's not a nitro backed instance type and...

I've gone over the [GKE node reservation guide](https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-architecture#node_allocatable) (which EKS uses for CPU but not for memory) and the [K8s large clusters guide](https://kubernetes.io/docs/setup/best-practices/cluster-large/) which leaves me with the following question/statement....

For anyone wanting to solve this, the [--kube-reserved kubelet flag](https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#kube-reserved) will override the default values that _bootstrap.sh_ sets in _kubelet-config.json_.

@abeer91 could you or someone else working on this project please respond?