amazon-eks-ami
amazon-eks-ami copied to clipboard
Packer configuration for building a custom EKS AMI
**What would you like to be added**: Install crictl as part of the EKS AMI build. Currently the only CLI utility included with the AMI is ctr. crictl project: https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md...
**What happened**: According to the [Kubernetes 1.11 documentation](https://github.com/kubernetes/website/blob/5294779969e471b1d4897821af8eebe16af9401f/content/en/docs/tasks/administer-cluster/sysctl-cluster.md#enabling-unsafe-sysctls) ``` --allowed-unsafe-sysctls 'net.core.rmem_max' ``` should be a valid `kubelet` flag. We're currently passing this into EKS via `BootstrapArguments`: ```--kubelet-extra-args "--allowed-unsafe-sysctls 'net.core.rmem_max,net.core.netdev_max_backlog'"``` and...
This reintroduces the switch to use "aws eks get-token" instead of the aws-iam-authenticator. The reason (see [0]) why that switch got reverted was, that eksctl wasn't able to handle the...
There was an issue my kernel version 5.4.176-91.338.amzn2 (some ami prior to march 9th) where the ephemeral port range was starting from 0 to 65535. They should be starting above...
**What happened**: System OOM happens in some of nodes after upgrade to ks8 1.19 (using AMI v20210414). It seems this happens more for bigger nodes, like r5.4x and r5.8x. ```...
*Issue #99 *Description of changes:* See CIS Benchmark 4.2.9 By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of...
*Description of changes:* Use `aws sts get-caller-identity` to check whether AWS CLI is installed, rather than the presence of an unnecessary AWS_ACCESS_KEY_ID variable (instance profiles, AWS CLI profiles, and others...
**What would you like to be added**: Right now, bootstrap.sh accepts extra kubelet flags. That's not nice if the thing we try to configure is hard to express via flags,...
**What happened**: Deployed an IPv6 enabled EKS cluster using https://github.com/terraform-aws-modules/terraform-aws-eks **What you expected to happen**: IPv6 DNS to correctly be set, instead it is using the 172.x.x.x address **How to...
*Issue #, if available:* No Issue # created *Description of changes:* * Add a .editorconfig file * Fix `--enable-docker-bridge` -- without this change DNS does not seem to work with...