Last few months I experimented more and more with all OpenEBS solutions that fit small Kubernetes cluster, using MicroK8S and Hetzner Cloud for a real experience. - Source: dev.to / over 1 year ago

I would investigate https://openebs.io/ https://portworx.com/ https://longhorn.io/ if you are forced to you can mount ISCSI on the kublet and feed it to one of those solutions. Keep in mind most of the big guys buy some sort of managed solution that you can point a CSI like trident https://netapp-trident.readthedocs.io. Source: almost 2 years ago

What are some cool projects to self hosted on a home Raspberry Pi (64 bit) Kubernetes cluster (Helm charts). Arm64 support is a must. A lot of projects only build amd64 Docker containers which don't run on my cluster. I currently run:

   - obenebs (provides abstraction for using local k8s worker disks as PVC mounts when running on-prem) -- https://openebs.io/.

- Source: Hacker News / about 2 years ago

What do you use to provision Kubernetes persistent volumes on bare metal? I’m looking at open-ebs (https://openebs.io/). Also, when you bump the image tag in a git commit for a given helm chart, how does that get deployed? Is it automatic, or do you manually run helm upgrade commands? - Source: Hacker News / over 2 years ago

Ideas from my kubernetes experience: * Cert-Manager is very popular and almost a must-have if you terminate SSL inside the cluster * Backups using velero * A dashboard/UI is actually very helpful to quickly browse resources, client tools like k9s are fine too * Secret: Management: Bitnami Sealed Secrets is the second big project in that space * I would add Loki to aggregate Logs * Never heard of ory. Usually I see... Source: over 2 years ago

In today's world of cloud computing, AWS Lambda is a serverless, event-driven compute service that lets you run code for virtually any type of application or backend service without provisioning or managing servers. You can trigger Lambda from over 200 AWS services and software as a service (SaaS) applications, and only pay for what you use. - Source: dev.to / 7 days ago

The first reason is that serverless architectures are inherently scalable and elastic. They automatically scale up or down based on the incoming workload without requiring manual intervention through serverless compute services like AWS Lambda, Azure Functions, or Google Cloud Functions. - Source: dev.to / 10 days ago

On this day, we both first learned about Lambda. This was the world's first public Functions-as-a-Service platform, better known as FaaS. They told us that this was the next evolution in Cloud Computing. With Lambda, you could now host snippets of code on AWS. There were no more idle workers, and you could auto-scale with minimal additional configuration required. Also, these snippets were event-driven by nature.... - Source: dev.to / 18 days ago

AWS Lambda simplifies composable applications by offering serverless execution, seamless integration with AWS services, automatic scaling, and cost efficiency without the need to manage servers. - Source: dev.to / 23 days ago

Deploying Dart functions to AWS Lambda enables you to utilize them not only within AWS Lambda but also integrate them with services like Amazon API Gateway, allowing you to leverage them in Flutter applications as well. This unified codebase in Dart offers great convenience. - Source: dev.to / 23 days ago