keptn VS podtato-head

One of the other places I spent a lot of time at at KubeCon NA was the CNCF Project Pavillion. I was very happy to see that it was a bit larger than the area we had during KubeCon EU, but I still wish that it was bigger and wasn’t so tucked away in the corner. A number of booths were showcasing their projects with demos through the week, hosted Q&A time, and gave away swag. If you are still trying to understand the Cloud Native Ecosystem, you can look at this very extensive map of the landscape and projects under the CNCF, some of which are more advanced than others. Of course I’m biased, but I’m really excited for the work that Keptn is doing in helping developers have more control over their application lifecycle. I’m also very excited to see where Backstage goes and how other CNCF projects can integrate with their service catalog.

I can’t speak from experience, but I think Keptn might be worth looking into: https://keptn.sh/

Go try this out and share your feedback on what you like about this integration and what you’d like improved. Feel free to create issues, engage in discussions on the Keptn Slack and Litmus Github repository. Stay tuned for more updates on how you can leverage Keptn & LitmusChaos CNCF projects to build and ship resilient cloud-native applications!

If you want, you can also manually download the binary file from Github and install the CLI by moving it into your path.

You should checkout Podtato Head from the CNCF. It has a bunch of different deployment scenarios. https://github.com/podtato-head/podtato-head

https://github.com/podtato-head/podtato-head has great examples of deploying an app using different methods.

Automated deployment of an application via Keptn is typically chained with CI pipelines that generate the images or resource artifacts. In our use-case, the goal is to examine the resilience of one such helloservice application: the CNCF podtato-head. The hypothesis as a developer or user of the helloservice is that (a) the app is nearly always available and (b) accessed within a desired latency. We shall use a pod-kill chaos experiment to disrupt the state and verify if our resilience hypothesis holds true (i.e., whether the service has been built/deployed to meet our expectations). This action is performed when the application is busy serving requests, as this is a real-world case.

git clone https://github.com/cncf/podtato-head.git