epinio VS fission

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

Fission

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.

I use https://fission.io/ on Kubernetes to emulate AWS Lambda + API Gateway to run Python functions. I use their YAML Spec functionality to deploy functions. It works well for my use case.

After doing a lot of research, I ended up settling on the Fission.io framework to support this project. Fission is an open-source Serverless framework running in kubernetes. Think AWS Lambdas, but we are in control of every part of the infrastructure. Kubernetes gives us the power to define the environments the containers will be executed in, and any other resources they need. This gives us the control we need to be able to create our very own environment for executing arbitrary JavaScript through the V8 engine. Each function can be isolated as much as we need to and Fission is really great at giving us the ability to quickly create multiple environments.

Nope. I was using https://fission.io/

There are a lot of FaaS service offerings out there namely Lambda, Azure Functions, Google Cloud Functions to name a few. While these offerings run on their respective clouds, there are services like Fission that are open source and allow you to deploy and execute functions on Kubernetes clusters irrespective of where they reside.

Fission

It's super slow (20-50 rps), please try this instead : https://github.com/fission/fission (few hundreds to few thousands rps)