amazon-eks-custom-amis
amazon-eks-ami
Our great sponsors
| amazon-eks-custom-amis | amazon-eks-ami | |
|---|---|---|
| 1 | 19 | |
| 178 | 2,336 | |
| 0.6% | 1.2% | |
| 4.0 | 9.2 | |
| 6 months ago | 5 days ago | |
| Shell | Shell | |
| MIT No Attribution | MIT No Attribution |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
amazon-eks-custom-amis
-
Hardening EKS nodes?
There is this reference project which shows how to do it - it does require some updating to make it current however https://github.com/aws-samples/amazon-eks-custom-amis
amazon-eks-ami
-
Compile Linux Kernel 6.x on AL2? 😎
For example, this is available for AL2: https://github.com/awslabs/amazon-eks-ami
-
k3s on AWS,does it make sense?
source
- EKS Worker Nodes on RHEL 8?
-
Blog: KWOK: Kubernetes WithOut Kubelet
# of pods are essentially capped by the worker node choice.
below excerpt from: https://github.com/awslabs/amazon-eks-ami/blob/master/files/...
# Mapping is calculated from AWS EC2 API using the following formula: -
Tips on working with EKS
See also: EKS nodes lose readiness when containers exhaust memory
-
Implement DevSecOps to Secure your CI/CD pipeline
Use a hardened image for the worker server. All cloud providers provide CIS benchmark harden images. We can also build our own custom hardened image using amazon-eks-ami.
-
EKS node t4g.medium has a pod limit of 11, but should be 17
Check via this script: https://github.com/awslabs/amazon-eks-ami/blob/master/files/max-pods-calculator.sh
-
Hardening EKS nodes?
Forgive me cause I'm not very familiar with EKS, can EKS consume these AMIs or do we need separate EKS-compatible ones? eg. it appears to be discussed here without a solution https://github.com/awslabs/amazon-eks-ami/issues/245
-
DNS timeout on EKS
I saw that there was a race condition issue some time ago https://github.com/awslabs/amazon-eks-ami/issues/357 but it got fixed at some point. My resolv.conf file looks like this in one of my pod:
What are some alternatives?
calico - Cloud native networking and network security
amazon-eks-pod-identity-webhook - Amazon EKS Pod Identity Webhook
amazon-vpc-cni-k8s - Networking plugin repository for pod networking in Kubernetes using Elastic Network Interfaces on AWS
distroless - 🥑 Language focused docker images, minus the operating system.
prometheus - The Prometheus monitoring system and time series database.
skopeo - Work with remote images registries - retrieving information, images, signing content
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
envoy - Cloud-native high-performance edge/middle/service proxy
Visual Studio Code - Visual Studio Code
JaCoCo - :microscope: Java Code Coverage Library
terraform-provision-gke-cloudflare
Metasploit - Metasploit Framework