epinio VS pack

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

I've recently found this quote by Kelsey Hightower:

"I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."

Source: https://twitter.com/kelseyhightower/status/85193508753294540...

In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.

My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.

Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?

Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.

Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?

```bash (curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.28.0/pack-v0.28.0-linux-arm64.tgz" | sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack)

Although Dockerfiles have the benefit of migrating existing workloads to containers without having to update your toolchain, I definitely prefer the container-first workflow. Cloud Native [Buildpacks](https://buildpacks.io/) are a CNCF incubating project but were proven at Heroku. Buildpacks support common languages, but working on a Go project I've also had a great experience with [ko](https://ko.build/). Free yourself from Dockerfile!

Cloud Native Buildpacks

It's big and overwhelming and sometimes scary. But you know what? It's also fun, engaging, and very refreshing. Because I'm a DevRel, I don't have many chances to focus on something particular. Still, I'm having a lot of fun exploring different CMSs (like Statamic, Craft, or Sanity), new approaches (at last, I understood why the headless approach is so important), and diving into tech I never used before (hello Buildpacks).