From cce972d40495c685a1f5d040c8ae943152d54062 Mon Sep 17 00:00:00 2001 From: Scott Nichols Date: Thu, 14 Jan 2021 15:41:28 -0800 Subject: [PATCH] Update README.md --- README.md | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 0eea540..6e05352 100644 --- a/README.md +++ b/README.md @@ -74,12 +74,15 @@ After this is all installed, you will have an eventing topology like this: And sends this to the Knative Eventing Broker "default". 1. The Knative Eventing Broker delivers the CloudEvent to all matching triggers, in our case two: - - The `drop` service filters events and for the Rule `Terminal shell in container`, deletes the pod: - > [Terminal shell in container] deleted mysql-db-7d59548d75-wh44s from default because 23:48:20.851908334: Notice A shell was spawned in a container with an attached terminal (user=root user_loginuid=-1 k8s.ns=default k8s.pod=mysql-db-7d59548d75-wh44s container=f29b261f8831 shell=bash parent=runc cmdline=bash -il terminal=34816 container_id=f29b261f8831 image=mysql) k8s.ns=default k8s.pod=mysql-db-7d59548d75-wh44s container=f29b261f8831 - And this knocks the shell off the deleted pod: - ``` - (╯°□°)╯︵ kubectl exec -it $(kubectl get pods --selector="app=mysql-db" --output=jsonpath={.items..metadata.name}) -- bash -il - root@mysql-db-7d59548d75-89v4c:/# command terminated with exit code 137 - ``` - - `Sockeye` also recieves the event and displays it: - ![Sockeye showing the CloudEvent](./img/sockeye.png) + +- The `drop` service filters events and for the Rule `Terminal shell in container`, deletes the pod: + > [Terminal shell in container] deleted mysql-db-7d59548d75-wh44s from default because 23:48:20.851908334: Notice A shell was spawned in a container with an attached terminal (user=root user_loginuid=-1 k8s.ns=default k8s.pod=mysql-db-7d59548d75-wh44s container=f29b261f8831 shell=bash parent=runc cmdline=bash -il terminal=34816 container_id=f29b261f8831 image=mysql) k8s.ns=default k8s.pod=mysql-db-7d59548d75-wh44s container=f29b261f8831 + + And this knocks the shell off the deleted pod: + + ``` + (╯°□°)╯︵ kubectl exec -it $(kubectl get pods --selector="app=mysql-db" --output=jsonpath={.items..metadata.name}) -- bash -il + root@mysql-db-7d59548d75-89v4c:/# command terminated with exit code 137 + ``` +- `Sockeye` also recieves the event and displays it: + ![Sockeye showing the CloudEvent](./img/sockeye.png)