Add showcase framework

[bwplotka]

CI that will ensure all showcases generated the same output (e.g Kubernetes YAMLs)

[bwplotka]

I was thinking about our Thanos deployment. Another idea (we can do both) from @metalmatze to do simpler example than this.

[metalmatze]

This entire effort reminds me of a lot of the TodoMVC project where the JavaScript community compares different frameworks to, in the end, achieve the same application.

It would be good to come up with a very concise plain YAML example that still introduces enough complexity. Like, we want a Deployment, Service for a simple application. First layer of complexity would be to generate two very similar but still different directories for staging and production environments.

[metalmatze]

The example application could actually be this: https://kubernetes.io/docs/tutorials/stateless-application/guestbook/

Then have a bit more complexity by generating for staging and production with different replicas etc.

[RiRa12621]

i think Thanos might be a bit overkill.
Part of the effort imho should be to keep everything comprehensive, which might be significantly harder if you first have to understand the show case itself.
I'd agree with something like @metalmatze proposed.

[bwplotka]

We can have both. We are looking configuration that will work for overkill cases not for simple cases. (:

…

On Tue, 28 Apr 2020 at 16:04, Rick Rackow ***@***.***> wrote: i think Thanos might be a bit overkill. Part of the effort imho should be to keep everything comprehensive, which might be significantly harder if you first have to understand the show case itself. I'd agree with something like @metalmatze <https://github.com/metalmatze> proposed. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVA3O32JJ3VGNGDIOBP73DRO3V6HANCNFSM4LW7RS3A> .

[RiRa12621]

+1 for both