podtato-head
spec
| podtato-head | spec | |
|---|---|---|
| 5 | 31 | |
| 340 | 4,788 | |
| -0.3% | 2.1% | |
| 1.3 | 7.6 | |
| about 2 months ago | 4 days ago | |
| Shell | Python | |
| 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.
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
spec
-
Data Streaming Architecture
The structure of this example message is using CloudEvents specification:
- CloudEvents Event Specification
-
Microsoft Azure Event Grid MQTT Protocol Support and Pull Message Delivery Are Now in Public Preview
Microsoft has expanded the Event Grid capabilities to enhance system interoperability by introducing support for MQTT v3.1.1 and v5.0 protocols. This allows customers to publish and subscribe to messages for Internet of Things (IoT) solutions. This new support, currently available in public preview, complements the existing support for CloudEvents 1.0.
-
OpenTelemetry for Open Source Telemetry?
You are looking for https://cloudevents.io/ . That is what you should use if you plan to do homegrown. I would however recommend you to use use segment + amplitude, juno, mixpanel . If you are early these are mostly free up to a point.
- FLaNK Stack Weekly 27 March 2023
-
Format of a Kafka message envelope
When modeling an event in a streaming application, what "meta" fields to you use? Like timestampts, versions, some context etc... I think there are some efforts to introduce a standard format like Cloud Events but wondering if you guys have any different suggestions?
-
Show HN: Automatisch – open-source workflow automation, an alternative to Zapier
CloudEvents is trying to standardize on the messaging
https://cloudevents.io/
- FLiP Stack Weekly for 21 Jan 2023
- cloudevents: A specification for describing event data in a common way
-
A message queue focus on serverless program
Hello guys, actually, vanus can directly deliver messages to OpenFaaS without this kind of connector. Because vanus can deliver messages that follow the CloudEvents standard, OpenFaaS can also receive such messages. More details https://docs.linkall.com/how-to/use-gcloud-functions
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.
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
asyncapi-to-postman - Creates a Postman collection from an AsyncAPI file.
spring-petclinic - A sample Spring-based application
cupid - A library that focuses on finding and analyzing the relationships between AsyncAPI documents. It outputs a map of the system architecture. Except for a default map, it is possible to get output as mermaid.js flow diagram, PlantUML class diagram and more to come.
litmus - A fast python HTTP server inspired by japronto written in rust.
youtube-websub-subscription-handler - This is a WebSub subscription handler for YouTube video feed update | YouTube 비디오 피드 업데이트를 WebSub 기능을 이용해 받아 처리합니다
litmus-service - Integration for LitmusChaos
generator - Use your AsyncAPI definition to generate literally anything. Markdown documentation, Node.js code, HTML documentation, anything!
prometheus-service - Keptn service for utilizing Prometheus monitoring and alerting in keptn
k8s-event-grid-bridge - A simple event bridge for Kubernetes native events to Azure Event Grid.