服务向多个Knative Broker发送事件的正确方式及配置疑问

不用硬编码Broker URL，有几个更优雅的方式解决你的问题：

1. 给每个SinkBinding配置自定义环境变量 #

默认SinkBinding只会注入K_SINK，但你可以通过自定义环境变量名，让多个SinkBinding分别注入不同Broker的地址。

比如给两个Broker分别创建SinkBinding：

# 绑定default命名空间的broker-a，注入为K_SINK_BROKER_A
apiVersion: sources.knative.dev/v1
kind: SinkBinding
metadata:
  name: binding-broker-a
spec:
  subject:
    apiVersion: apps/v1
    kind: Deployment
    name: 你的服务部署名
  sink:
    ref:
      apiVersion: eventing.knative.dev/v1
      kind: Broker
      name: broker-a
      namespace: default
  env:
    - name: K_SINK_BROKER_A
      valueFrom:
        fieldRef:
          fieldPath: status.address.url

# 绑定other-ns命名空间的broker-b，注入为K_SINK_BROKER_B
apiVersion: sources.knative.dev/v1
kind: SinkBinding
metadata:
  name: binding-broker-b
spec:
  subject:
    apiVersion: apps/v1
    kind: Deployment
    name: 你的服务部署名
  sink:
    ref:
      apiVersion: eventing.knative.dev/v1
      kind: Broker
      name: broker-b
      namespace: other-ns
  env:
    - name: K_SINK_BROKER_B
      valueFrom:
        fieldRef:
          fieldPath: status.address.url

这样你的服务Pod里就会同时有K_SINK_BROKER_A和K_SINK_BROKER_B两个环境变量，代码里直接根据业务逻辑选择对应的地址发送事件即可。

2. 用Trigger做事件路由，服务只发默认Broker #

如果你的服务不需要直接指定多个Broker，可以让它统一把事件发送到一个默认Broker（通过默认的K_SINK），然后配置多个Trigger，根据事件的属性（比如type、source）自动把事件转发到不同的目标Broker（包括跨命名空间的），最终由这些Broker投递到对应的Kafka Topic。

示例Trigger配置：

# 把type为com.yourcompany.event.typeA的事件转发到broker-a
apiVersion: eventing.knative.dev/v1
kind: Trigger
metadata:
  name: trigger-to-broker-a
  namespace: default
spec:
  broker: default-broker
  filter:
    attributes:
      type: com.yourcompany.event.typeA
  subscriber:
    ref:
      apiVersion: eventing.knative.dev/v1
      kind: Broker
      name: broker-a
      namespace: default

# 把type为com.yourcompany.event.typeB的事件转发到other-ns的broker-b
apiVersion: eventing.knative.dev/v1
kind: Trigger
metadata:
  name: trigger-to-broker-b
  namespace: default
spec:
  broker: default-broker
  filter:
    attributes:
      type: com.yourcompany.event.typeB
  subscriber:
    ref:
      apiVersion: eventing.knative.dev/v1
      kind: Broker
      name: broker-b
      namespace: other-ns

这种方式不需要修改服务代码，只靠Knative的Trigger规则就能完成路由，适合事件类型明确的场景。

3. 跳过Broker，直接用KafkaSink投递到指定Topic #

既然你的最终目标是把事件发到不同的Kafka Topic，完全可以跳过Broker这一层，直接用Knative的KafkaSink绑定服务，每个KafkaSink对应一个Topic，同样通过自定义环境变量注入地址。

示例KafkaSink和SinkBinding配置：

# 定义对应topic-x的KafkaSink
apiVersion: eventing.knative.dev/v1alpha1
kind: KafkaSink
metadata:
  name: kafka-sink-topic-x
  namespace: default
spec:
  bootstrapServers:
    - kafka-cluster-kafka-bootstrap.kafka:9092
  topic: topic-x

# 绑定KafkaSink到服务，注入为K_SINK_KAFKA_TOPIC_X
apiVersion: sources.knative.dev/v1
kind: SinkBinding
metadata:
  name: binding-kafka-topic-x
spec:
  subject:
    apiVersion: apps/v1
    kind: Deployment
    name: 你的服务部署名
  sink:
    ref:
      apiVersion: eventing.knative.dev/v1alpha1
      kind: KafkaSink
      name: kafka-sink-topic-x
  env:
    - name: K_SINK_KAFKA_TOPIC_X
      valueFrom:
        fieldRef:
          fieldPath: status.address.url

同理配置另一个KafkaSink对应topic-y，注入K_SINK_KAFKA_TOPIC_Y，服务直接向这些地址发送事件就能直达目标Topic，减少中间环节。

内容的提问来源于stack exchange，提问作者evhfla