eks-distro VS containers-roadmap

EKS Distro is an open source project on GitHub. You can check out the repository at this link. https://github.com/aws/eks-distro/

I work on EKS Anywhere and familiar with those options but my answer will be biased

EKS Anywhere provides a CLI, packaged Cluster API, and other tools (CNI, GitOps) on top of raw Kubernetes. K8s, k3s, k0s are binaries you have to manage and are similar to EKS Distro [1] which we publish and build on top of.

EKS Anywhere is designed to give you clusters you can manage long term using Cluster API and a full suite of tools for how we thing Kubernetes clusters should be run based on our experience running EKS. It is a closer comparison to Rancher's RKE or VMware Tanzu for provisioning clusters, but some features and implementation details are different.

1: https://distro.eks.amazonaws.com/

EKS Anywhere builds on the strengths of Amazon EKS Distro, the same open-source distribution of Kubernetes that is used by Amazon EKS on the cloud, thus fostering consistency and compatibility between clusters both on AWS as well as on-premises.

yes im aware of bmctl. however you dont have control over the kubernetes distro that's running.

is there anything similar to https://github.com/aws/eks-distro ?

EKS-A focuses on cluster management for HA environments. By default we use 3 etcd nodes, 2 control plane nodes, and 3 worker nodes. It uses cilium as the default CNI and Cluster API controllers for continual cluster state management. It has some optional configuration for a flux controller and OIDC authentication but it doesn't add default services or workloads. EKS-A also uses EKS Distro which is the open source Kubernetes distribution we run in hosted EKS.

Well almost... announcement and GitHub issue

EKS Anywhere is not released. It is “coming soon” and is based on EKS Distro. Distro is OSS. Anywhere will be supported at GA release.

There are requests to integrate Service Connect with Lambda and VPC Lattice. While this might be challenging due to architectural and conceptual reasons, if realized, it would significantly expand Service Connect's possibilities.

As mentioned earlier, pull-through cache checks for updates on the upstream side on a tag-by-tag basis every 24 hours. If you have enabled immutability for image tags in your ECR repository, which prevents overwriting images with the same tag, there is a concern that the cache might not update. However, there have been issues reported (see pull through cache rule related cache repository's immutability not ...) where image replacement still occurs even when immutability is enabled. This is something to be aware of when using the feature.

Thanks for showing up and answering questions. Congratulations on the release.

What kind of plans for support of Rust's evolving async ecosystem?

Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps? See example for Containers: https://github.com/aws/containers-roadmap/projects/1

Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically

Second, We will only rely on one managed node group, but we will leverage Karpenter; however, karpenter needs to be deployed on a node. (This may change soon once the Karpenter is available on the EKS Control Plane.) [EKS] Karpenter inside control plane · Issue #1792 · aws/containers-roadmap

As written in the AWS documentation, during periods of extremely high demand, Fargate Spot capacity might be unavailable. In concrete terms, if your ECS service is set up to execute tasks in 100% Spot, there is a risk of running out of capacity. A workaround has been created in the hope that one day this issue will be implemented by the AWS team. This workaround allows you to set up two ECS services :

Deploying Fargate with CDK has to have been the most pleasant developer experience I have ever had with any product so far.

If image caching becomes a reality with Fargate I can't imagine a need to ever use anything else

https://github.com/aws/containers-roadmap/issues/696

Eks Fargate doesn't support spot yet https://github.com/aws/containers-roadmap/issues/622