From c528d2c39f1c1d6430f7faccc7e6cf8b2938132d Mon Sep 17 00:00:00 2001 From: Phil Estes Date: Tue, 5 Oct 2021 16:13:22 -0400 Subject: [PATCH] Update ADOPTERS.md with additional uses Signed-off-by: Phil Estes --- ADOPTERS.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ADOPTERS.md b/ADOPTERS.md index 4d70cca63..0deb4b6ef 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -16,6 +16,10 @@ including the Balena project listed below. **_[AWS Fargate](https://aws.amazon.com/fargate)_** - uses containerd + Firecracker (noted below) as the runtime and isolation technology for containers run in the Fargate platform. Fargate is a serverless, container-native compute offering from Amazon Web Services. +**_[Amazon Elastic Kubernetes Service (EKS)](https://aws.amazon.com/eks/)_** - EKS optionally offers containerd as a CRI runtime starting with Kubernetes version 1.21. In Kubernetes 1.22 the default CRI runtime will be containerd. + +**_[Bottlerocket](https://aws.amazon.com/bottlerocket/)_** - Bottlerocket is a Linux distribution from Amazon Web Services purpose-built for containers using containerd as the core system runtime. + **_Cloud Foundry_** - The [Guardian container manager](https://github.com/cloudfoundry/guardian) for CF has been using OCI runC directly with additional code from CF managing the container image and filesystem interactions, but have recently migrated to use containerd as a replacement for the extra code they had written around runC. **_Alibaba's PouchContainer_** - The Alibaba [PouchContainer](https://github.com/alibaba/pouch) project uses containerd as its runtime for a cloud native offering that has unique isolation and image distribution capabilities.