litmus-service
podtato-head
Our great sponsors
litmus-service | podtato-head | |
---|---|---|
1 | 5 | |
7 | 340 | |
- | 0.3% | |
0.0 | 1.3 | |
8 months ago | about 2 months ago | |
Go | Shell | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
litmus-service
-
Part-2: Evaluating Application Resiliency with Keptn and LitmusChaos (use-case and demo)
The content has been adapted from demonstrations made to the cloud-native community during the CNCF SIG-App-Delivery & Keptn Webinars. Having said that, we will try to focus more on the “why” & “what” part of this demonstration than the “how” (steps, commands, and manifests involved). You can find details of the latter in this excellent tutorial from the Keptn team or find your way in the Github repository for the litmus-service.
podtato-head
-
any good repo to do some projects?
You should checkout Podtato Head from the CNCF. It has a bunch of different deployment scenarios. https://github.com/podtato-head/podtato-head
-
Recommended tutorial on setting up a generic web app so i can better understand cicd and app lifecycle
https://github.com/podtato-head/podtato-head has great examples of deploying an app using different methods.
- podtato-head/podtato-head: Demo App for TAG App Delivery
-
Part-2: Evaluating Application Resiliency with Keptn and LitmusChaos (use-case and demo)
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.
-
Modern continuous delivery on Kubernetes for developers
git clone https://github.com/cncf/podtato-head.git
What are some alternatives?
keptn - Cloud-native application life-cycle orchestration. Keptn automates your SLO-driven multi-stage delivery and operations & remediation of your applications.
prometheus-service - Keptn service for utilizing Prometheus monitoring and alerting in keptn
litmus - Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
spring-petclinic - A sample Spring-based application
litmus - A fast python HTTP server inspired by japronto written in rust.
Heimdall - An Application dashboard and launcher
prometheus-sli-service
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
docker-development-youtube-series