kots VS OpenFaaS

KOTS (by Replicated, mentioned already)

Check out https://kots.io/

We have helped clients several industries and sectors where these words either mean different things, or people who use them are thinking of different things. An appliance has meant a physical thing before it has also meant a VM.

The question you have asked includes a solution. Many client meetings start with that. This is what's called an XY problem[0], where the client says they want want Y, but that's their implementation of a solution to solve X. That may or may not be the only solution, but finding out the actual problem to be solved has never hurt me and saved a lot of time and money.

This is why we spend time defining the problem and stripping away every ounce of jargon we can, because that jargon can create a bias towards a solution that may not be optimal. For example, site-to-site VPN. Why? Gateway ? Why ? These are solutions. What's the job to be done.

Anyway... Have a look at https://www.replicated.com/ and https://kots.io/

0: https://github.com/replicatedhq/kots/pull/511

Serverless functions are now offered by many cloud providers, as well as having options like OpenFaaS, Knative, Apache's Openwhisk and more from the open source community that run in environments ranging from one server all the way up to globally replicated private clusters.

OpenFaaS

Did you consider running knative or openfaas? https://github.com/openfaas/faas

Anyone knows other alternatives for Azure Functions, but for DIY hosting? ( eg. OpenFaas - https://www.openfaas.com/ )

Maybe OpenFaaS with grafana and slack notifications for non-200 responses?

OpenFaaS - https://www.openfaas.com

By the way, if your organization is leveraging EKS as a platform and your DevOps team is willing to enable this operator, there's an exciting tool called OpenFaaS. Essentially, it enables you to host your Lambda functions on your own infrastructure instead of relying on the public cloud provider.

This is where I see K8S coming in – teachers can provide dev deployments that are setup for students to learn. Teachers can also provide containers that run automated tests against the student containers for assessment! Plus, we can smooth over some of the git workflow stuff for the ripest of beginners; we can integrate with github to sync their work on our platform to repositories on their github account, so that they can really take ownership of the work they do on the platform. Last, students can graduate their work from development into production very easily, since we can take the base images + student diffs, build a new "prod" image for the student. We can run students' prod work on "serverless" K8S frameworks like fission or OpenFaas to be able to host many low-traffic "production" apps at the same time.