How will this project sustain itself?

[sekka1]

Working on this project will take time. Who or what will pay for that time?

Ideals on how this project can monetize and sustain itself

A reference design to support consulting work

The reference design is mostly working and very generic. If you wanted to use the open source stuff and integrate it yourself then it is free. If you like this but don't want to spend your own time on integrating it in with your CI/CD system, the consulting side will help you do that and also maintain the setup for you.

Some type of SaaS service

Running the full test create pipeline

The pipeline:

• create a new cluster of a version
• update the cluster's version or with the changes
• Run the e2e tests
• Post results

How would we do this in a generic fashion for everyone? We would have to know how the cluster works. This probably means, we will prescribe a way to build a cluster with Kops, eksctl, GKE and then we would apply this process on it.

Our way of instantiating a cluster would most likely be very opinionated to be able to make this work for everyone and maintainable.

Would that work? Would people use our way of instantiating a cluster to get this pipeline?

This would also be in a very critical path of the user's workflow and be a very important piece of software because essentially this would be creating and updating their kube cluster which is running their own software.

I think it is a big downside to be such an important piece of software for a life style business. People would have to trust that you will be around for the long run.

Something less than the full test create pipeline?

Can the SaaS part take on something less? This might also make it easier to create.

If we just maintained the e2e tests with the extra live testing in your cluster like bring up a statefulest, setup prometheus, etc. Could that be an offering?