解密开源Serverless容器框架：事件驱动篇

apiVersion: eventing.knative.dev/v1kind: Brokermetadata:  generation: 1  name: default  namespace: defaultspec:  config:    apiVersion: v1    kind: ConfigMap    name: config-br-default-channel    namespace: knative-eventing  delivery:    backoffDelay: PT0.2S    backoffPolicy: exponential    retry: 10status:  address:    name: http    url: http://broker-ingress.knative-eventing.svc.cluster.local/default/default  annotations:    knative.dev/channelAPIVersion: messaging.knative.dev/v1    knative.dev/channelAddress: http://default-kne-trigger-kn-channel.default.svc.cluster.local    knative.dev/channelKind: InMemoryChannel    knative.dev/channelName: default-kne-trigger  ...

http://default-kne-trigger-kn-channel.default.svc.cluster.local

kubectl get svc default-kne-trigger-kn-channelNAME                             TYPE           CLUSTER-IP   EXTERNAL-IP                                         PORT(S)   AGEdefault-kne-trigger-kn-channel   ExternalName   <none>       imc-dispatcher.knative-eventing.svc.cluster.local   80/TCP    98m

prapiVersion: messaging.knative.dev/v1kind: InMemoryChannelmetadata:  labels:    eventing.knative.dev/broker: default    eventing.knative.dev/brokerEverything: "true"  name: default-kne-trigger  namespace: default  ownerReferences:  - apiVersion: eventing.knative.dev/v1    blockOwnerDeletion: true    controller: true    kind: Broker    name: default    uid: cb148e43-6e6c-45b0-a7b9-c5b1d81eeeb6spec:  delivery:    backoffDelay: PT0.2S    backoffPolicy: exponential    retry: 10  subscribers:  - delivery:      backoffDelay: PT0.2S      backoffPolicy: exponential      retry: 10    generation: 1    replyUri: http://broker-ingress.knative-eventing.svc.cluster.local/default/default    subscriberUri: http://broker-filter.knative-eventing.svc.cluster.local/triggers/default/my-service-trigger/f8df36a0-df4c-47cb-8c9b-1405111aa7dd    uid: 382fe07c-ce4d-409b-a316-9be0b585183astatus:  address:    name: http    url: http://default-kne-trigger-kn-channel.default.svc.cluster.local  ...  subscribers:  - observedGeneration: 1    ready: "True"    uid: 382fe07c-ce4d-409b-a316-9be0b585183a

apiVersion: eventing.knative.dev/v1kind: Triggermetadata:  labels:    eventing.knative.dev/broker: default  name: my-service-trigger  namespace: defaultspec:  broker: default  filter: {}  subscriber:    ref:      apiVersion: serving.knative.dev/v1      kind: Service      name: event-display      namespace: defaultstatus:  ...  observedGeneration: 1  subscriberUri: http://event-display.default.svc.cluster.local

curl -v "http://172.16.85.64/default/default" -X POST -H "Ce-Id: 536808d3-88be-4077-9d7a-a3f162705f79" -H "Ce-Specversion: 1.0" -H "Ce-Type: dev.knative.samples.helloworld" -H "Ce-Source: dev.knative.samples/helloworldsource" -H "Content-Type: application/json" -d '{"msg":"Hello World from the curl pod."}'

2024/09/23 03:25:23 receive cloudevents.Event: %!(EXTRA string=Validation: valid Context Attributes,   specversion: 1.0   type: dev.knative.samples.helloworld   source: dev.knative.samples/helloworldsource   id: 536808d3-88be-4077-9d7a-a3f162705f79   time: 2024-09-23T03:25:03.355819672Z   datacontenttype: application/json Extensions,   knativearrivaltime: 2024-09-23T03:25:23.380731115Z Data,   {     "msg": "Hello World from the curl pod."   } )

apiVersion: flows.knative.dev/v1kind: Sequencemetadata:  name: sequencespec:  channelTemplate:    apiVersion: messaging.knative.dev/v1    kind: InMemoryChannel  steps:    - ref:        apiVersion: serving.knative.dev/v1        kind: Service        name: first    - ref:        apiVersion: serving.knative.dev/v1        kind: Service        name: second    - ref:        apiVersion: serving.knative.dev/v1        kind: Service        name: third  reply:    ref:      kind: Service      apiVersion: serving.knative.dev/v1      name: event-display

apiVersion: flows.knative.dev/v1kind: Parallelmetadata:  name: demo-parallel  namespace: defaultspec:  branches:  - subscriber:      ref:        apiVersion: v1        kind: Service        name: demo-ksvc1        namespace: default  - subscriber:      ref:        apiVersion: v1        kind: Service        name: demo-ksvc2        namespace: default  channelTemplate:    apiVersion: messaging.knative.dev/v1    kind: InMemoryChannel

KEDA is a Kubernetes-based Event Driven Autoscaler. With KEDA, you can drive the scaling of any container in Kubernetes based on the number of events needing to be processed.

Knative Eventing is a collection of APIs that enable you to use an event-driven architecture with your applications.

apiVersion: sources.knative.dev/v1kind: PingSourcemetadata:  name: ping-sourcespec:  schedule: "* */1 * * *"  contentType: "application/json"  data: '{"model": "qwen", "messages": [{"role": "user", "content": "渴了"}], "max_tokens": 10, "temperature": 0.7, "top_p": 0.9, "seed": 10}'  sink:    ref:      apiVersion: flows.knative.dev/v1      kind: Sequence      name: sequence

apiVersion: flows.knative.dev/v1kind: Sequencemetadata:  name: sequencespec:  channelTemplate:    apiVersion: messaging.knative.dev/v1    kind: InMemoryChannel  steps:    - ref:        apiVersion: serving.knative.dev/v1        kind: Service        name: qwen  reply:    ref:      kind: Service      apiVersion: serving.knative.dev/v1      name: drink-svc

{"id":"cmpl-6251aab6a0dc4932beb82714373db2ac","object":"chat.completion","created":1733899095,"model":"qwen","choices":[{"index":0,"message":{"role":"assistant","content":"如果你感到口渴，可以尝试喝一些水"},"logprobs":null,"finish_reason":"length","stop_reason":null}],"usage":{"prompt_tokens":10,"total_tokens":20,"completion_tokens":10}}

apiVersion: serving.knative.dev/v1kind: Servicemetadata:  name: drink-svc  namespace: defaultspec:  template:    spec:      containers:      - image: registry.cn-hangzhou.aliyuncs.com/knative-sample/event-display:v1211-action        env:        - name: ACTION          value: "drink water"

# 日志输出结果如下所示：ACTION: drink water