Pankaj Walke

Here is the fix: **Solution:** Set the `tcp_keepalive` less than 350s e.g. tcp_keepalive=300. On Amazon Linux you can set this as shown below: ``` sudo sysctl net.ipv4.tcp_keepalive=300 ``` Also, you...

@TiberiuGC `nodeadm` does not allow passing just kubelet config via file, It has to be the entire `NodeConfig` and it has to be passed as `nodeadm config --config-source`. However, doing...

@TiberiuGC ~~I see, I think this should work. I will try to test it.~~ I just walked through the nodeadm code and I think, using `--config` in `nodeConfig.spec.kubelet.flags` may not...

Sure @TiberiuGC I will work on it.

@rwilson-release The difference you are noticing is expected because you started using ManagedNodeGroup and the `PropagateAtLaunch` is statically [set as `false`](https://github.com/eksctl-io/eksctl/blob/ce836e8774089fde63551ff69be7bec698bf5b47/pkg/cfn/manager/api.go#L265). However, ClusterAutoscaler (CAS) does not have any hard requirement...

@rwilson-release Thank you for pointing that out. > is it possible the unmanaged node groups are labeled correctly vs the managed? Even for unmanaged nodegroups, the taint effect was never...

🌟🌟🌟**Workaround for partially Air-Gapped VPCs**🌟🌟🌟 1. Create Route 53 [outbound endpoint](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-forwarding-outbound-queries.html#resolver-forwarding-outbound-queries-configuring) in VPC. 2. Create [Route53 Resolver Rule](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-rules-managing.html#resolver-rules-managing-viewing) and associated it under above Outbound endpoint and associate with the cluster...

#5498 is merged. @phoban01 or @seanschneeweiss you are good to go!

@phuhung273 Thank you for working on this. update: I have created a PR #5574 which will solve ServiceLimiter problem. You can find more details in it. On Side note: Looks...

> @punkwalker The reason i didn't use `awsmetricsv2.WithMiddleware` because it also include `recordAWSPermissionsIssue(target)` - which the V1 `NewGlobalSQSClient` doesn't have https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5562/files#diff-bc3c4b26fb02ca5f71b1e4bbcefb77736adcbefa0a5f1df66b48228bed9ecb7cL136-L139 > > So I created `WithRequestMetricContextMiddleware` with only `RequestMetric`....