eks-distro
eks-nvme-ssd-provisioner
Our great sponsors
| eks-distro | eks-nvme-ssd-provisioner | |
|---|---|---|
| 8 | 1 | |
| 1,334 | 62 | |
| 0.9% | - | |
| 9.8 | 0.0 | |
| 7 days ago | 2 months ago | |
| Shell | Shell | |
| Apache License 2.0 | MIT License |
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.
eks-distro
-
Using Amazon’s Kubernetes Distribution Everywhere with Amazon EKS Distro
EKS Distro is an open source project on GitHub. You can check out the repository at this link. https://github.com/aws/eks-distro/
-
Cubernetes
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.
- EKS is phasing out LoadBalancer type, what does this mean?
-
EKS Anywhere: The What, The Why and The How
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.
-
Amazon EKS Anywhere
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.
-
EKS or not?
Well almost... announcement and GitHub issue
-
EKS Anywhere & Disaster Recovery
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.
eks-nvme-ssd-provisioner
-
What's the recommended way to assign a large 'scratch' volume per-pod of a deployment, in a Cloud env like AWS EKS?
I'm fairly certain if you pick an instance type with local ssd you can set up a storage class to offer it as a local volume: https://github.com/brunsgaard/eks-nvme-ssd-provisioner
What are some alternatives?
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
gardener - Kubernetes-native system managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, OpenStack, vSphere, KubeVirt, Hetzner, EquinixMetal, MetalStack, and OnMetal with minimal TCO.
awesome-kubernetes - A curated list for awesome kubernetes sources :ship::tada:
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
aws-workflows-on-github - Workflows for automation of AWS services setup from Github CI/CD
gluster-kubernetes - GlusterFS Native Storage Service for Kubernetes
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
longhorn - Cloud-Native distributed storage built on and for Kubernetes
Nginx - An official read-only mirror of http://hg.nginx.org/nginx/ which is updated hourly. Pull requests on GitHub cannot be accepted and will be automatically closed. The proper way to submit changes to nginx is via the nginx development mailing list, see http://nginx.org/en/docs/contributing_changes.html