epinio VS OpenFaaS

You could have a look to https://epinio.io/. It is a PAAS that leverage build pack to deploy app on k8s cluster. Disclaimer: my team is working on it

Epinion

Would have helped if I spent it right 😂 - https://github.com/epinio/epinio

Epinio can be installed using Helm onto any compliant Kubernetes Cluster. The latest CLI release can be found at [][https://github.com/epinio/epinio/releases]

We are building a product (Epinio) to avoid this. The idea is that devs don't need to access the cluster and to know the Kubernetes internals to deploy something. It's still in alpha/beta, with a lot of development ongoing. 🙂

For the Apache/php container portion and building the app itself, I'd suggest looking at buildpacks (Paketo buildpacks are easy). This can let you standardize on the code->container pipeline. (I'm biased since I'm working on Epinio which uses them to simplify the code->running application pipeline)

For dev work, we also are working on a project called Epinio which takes a bit of a different approach to developing on top of Kubernetes. (https://epinio.io)

Your workflow describes the inner loop of development. Take a look at https://skaffold.dev that. If you can’t be bothered to learn how to write k8s manifests, epinio might be worth a shot. I tried it on some simple stuff and it worked but I doubt it’s usefulness in complex setups. https://github.com/epinio/epinio

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.