eks-distro VS OpenFaaS

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.

Main page (check out the function examples at the bottom - even bash is covered!): https://www.openfaas.com/

OpenFaaS

openfaas is fairly popular

Learning Kubernetes (K8s) for me was about getting pissed off enough at Bezos for all the money he was making off of me lol. I wanted to have my own little infrastructure that I control but without having to babysit it. I tried Docker Swarm, which was nice but wasn’t translating into professional-grade cluster experience. I found a project called Open FAAS that let me deploy my own Lambda/serverless. It ran on K8s. So, I followed a few tutorials on K3s (a lightweight version of K8s for the pi) and deployed it with K3sup. The OpenFAAS project, K8s, and Docker are written in Golang, so I learned some of that with A Tour Of Go. After branching out into the K8s world for a bit, I decided to get my Certified Kubernetes Application Developer (CKAD). I took this Udemy course and passed the test on the first go. You’ll learn just about everything you’ll need to know about K8s from that experience.

The call for MIT / Apache 2.0 licensing at the end of the post was surprising, given the issues that the author outlined.

Grafana and Minio have both moved to AGPL / dual licensing from permissive licenses to stimulate licensing sales and revenue. As the maintainer of OpenFaaS, it's been a struggle to correct the balance of corporations freeloading [0] vs. contributing code or finances.

GitHub Sponsors has also given very mixed results [1]

In the same week we saw the maintainer of a popular OSS work almost throw in the towel [2]

After 5 years, we're starting to see customer interest only by holding new features and enhancements back i.e. Open Core. There are still problems with this approach, and paying customers end up funding all the R&D required for the free users - amongst other things like competition from hobbyist users who covet features that are more appropriate in production than on your Raspberry Pi cluster.

[0] https://github.com/openfaas/faas/blob/master/ADOPTERS.md

If you're already using OpenFaaS, we'd love a PR to the ADOPTERS.md file to learn more about how you're using the project.

Functions-as-a-Service (eg. OpenFaaS).