GitXplorerGitXplorer
i

series-of-fortunate-cloudevents-kubecon2019

public
2 stars
1 forks
0 issues

Commits

List of commits on branch master.
Unverified
18757f6545d2a65cd37b9d4e8811222ba5a1e19d

add some base docs

iiancoffey committed 5 years ago
Unverified
1568db7c84f7a319b276498cd1da8d46dd11a00a

remove cruft

iiancoffey committed 5 years ago
Unverified
519986721594f1833518dbb6a8053eba1564663c

change event type to distracted

iiancoffey committed 5 years ago
Unverified
a7f4ad4d6925ae30869d3029f6d8bfceae41aebb

this is about to get wild me thinks

iiancoffey committed 5 years ago
Unverified
ff7c1706ec09c917e024c7efb6dcbc242e8c20ac

update readme

iiancoffey committed 5 years ago
Unverified
b1551b6dd1fa85b6f3da3918d4fdfe128a546e64

fix wand

iiancoffey committed 5 years ago

README

The README file for this repository.

kubecon-cloudevent-demo-app

This session will work to leverage CloudEvents and Knative Eventing to build a solution to automated conversations, with the conversation flow provided by the base projects.

New actors will boot and make themselves known to the group, and after this, they will begin conversing!

The actors only print to stdout what they hear, not what they said. So everything shown in the ./bin/listen script are events that have successfully reached the destination.

Pre-Reqs

Boot the demo system

The ./bin/up script will bring up the entire demo system for you, by creating a k8s cluster with Kind, installing knative via Gloo and create the necessary conversation details.

Create an actor

The bin/add_actor $NAME script will create and populate the namespace with a new actor, as well as the Knative Triggers necessary to allow them to join the conversation broker.

No other steps are needed for the actor to join the conversation. The actor is assigned a randomized script, which is mounted in a configmap.

They will address the whole group, or individuals who they know about.

Conversation

All of our actors are provided a conversation script, which lets them chat.

Log / Output Commands for demo

As you can see there is a lot going on:

kail -n work-conversations

kubectl logs -l "actor=fred" -n work-conversation --all-containers

kubectl describe containersource.sources.eventing.knative.dev -n work-conversation

KubeConfig

export KUBECONFIG="$(kind get kubeconfig-path --name="conversations")"