EKS News 019

In this issue, we’ll go over using AWS Proton for provisioning Amazon EKS, Mobileye’s usage of Amazon EKS (1000s of nodes), the differences between Docker, containerd, CRI-O and runc, and more.

Metric support now available in AWS Distro for OpenTelemetry

  • Today, we are announcing the general availability of AWS Distro for OpenTelemetry (ADOT) for metrics, a secure, production-ready, AWS-supported distribution of the OpenTelemetry project
  • [C]ustomers can use OpenTelemetry APIs and SDKs in Java, .Net, and JavaScript to collect and send metrics to Amazon CloudWatch, Amazon Managed Service for Prometheus, and other monitoring destinations supported by the OpenTelemetry Protocol (OTLP)
  • [P]art of the Cloud Native Computing Foundation (CNCF), OpenTelemetry provides open source APIs, libraries, and agents to collect distributed traces and metrics for application and infrastructure monitoring

Using AWS Proton as a provisioning mechanism for Amazon EKS clusters

  • AWS customers have a number of options they can use to deploy Amazon Elastic Kubernetes Service (Amazon EKS) clusters
  • If you are part of a team responsible for creating standards and governance for deployments while providing developers with self-service provisioning of Kubernetes clusters, this blog post is for you
  • [W]alk you through the benefits and the mechanics of using AWS Proton as a vending machine for Amazon EKS clusters
  • In a separate GitHub repository, we provide detailed, step-by-step instructions on how to create a vending configuration and deploy your first cluster

Mobileye’s journey towards scaling Amazon EKS to thousands of nodes

  • Mobileye develops self-driving technology and Advanced Driver Assistance Systems (ADAS) using state-of-the-art cameras, computer chips, and software
  • The managed service and managed node groups of Amazon EKS allowed us to focus on the workload instead of infrastructure, given a well-designed architecture based on our needs
  • Given the Amazon EKS architecture, our developers are not and should not be aware of the node group setup, Availability Zones, or any other aspects. To achieve that abstraction, we are using Argo Workflows.
  • One of the significant improvements that Karpenter brings is fast scaling (the time between the pod being created and the pod reaching a running state) and the fact that it does not require node groups, which at the scale of our architecture, can be challenging to manage.

Customizing scheduling on Amazon EKS

  • This post demonstrates how you can use a mutating pod admission webhook to customize pod scheduling across nodes
  • You can use this solution for a variety of use cases such as prioritizing nodes in an Availability Zone to reduce data transfer costs, spreading workloads across Availability Zones, or running workloads across On-Demand and Spot instances

Using SMB CSI Driver on Amazon EKS Windows nodes

Using IAM database authentication with workloads running on Amazon EKS

  • When running containerized workloads on Amazon EKS, it is common to store the stateful parts of the application outside of the Kubernetes cluster in one or more SQL or NoSQL databases
  • With Amazon Relational Database Service (Amazon RDS) and Amazon Aurora, the whole process of managing user access credentials can be simplified by using AWS Identity and Access Management (IAM) for authenticating to the database
  • In this blog post, we will demonstrate IAM database authentication with Amazon EKS by deploying a sample application and storing the state in an Amazon Aurora MySQL database

The differences between Docker, containerd, CRI-O and runc

  • Understanding Docker, The container ecosystem, explained, Docker Container Runtime Interface (CRI), Open Container Initiative (OCI)
  • All thoroughly covered in one place

KubeCon EU 2022 Wrap-Up | Flux

  • Daniel Holbach highlights KubeCon EU 2022
  • [E]verything you need to know about Flux and GitOps that happened there
  • Packed with tweets, talks, photos and more


  • ssh no ports provides ssh to a remote Linux device with out that device having any ports open
  • I found this tool this week and a bunch of different ideas popped into my head


  • A modern replacement for Redis and Memcached
  • Dragonfly is a modern in-memory datastore, fully compatible with Redis and Memcached APIs
  • Dragonfly implements novel algorithms and data structures on top of a multi-threaded, shared-nothing architecture
  • As a result, Dragonfly reaches x25 performance compared to Redis and supports millions of QPS on a single instance