Queue

KubeMQ Bridges Queue target provides a queue sender for processing sources requests.

Prerequisites

The following are required to run the queue target connector:

  • kubemq cluster

  • kubemq-bridges deployment

Configuration

Queue target connector configuration properties:

Example:

bindings:
  - name:  queue-binding 
    properties: 
      log_level: error
      retry_attempts: 3
      retry_delay_milliseconds: 1000
      retry_max_jitter_milliseconds: 100
      retry_delay_type: "back-off"
      rate_per_second: 100
    sources:
    .....
    targets:
      kind: target.queue # Sources kind
      name: 3-clusters-targets # targets name 
      connections: # Array of connections settings per each target kind
        - address: "kubemq-cluster-a-grpc.kubemq.svc.cluster.local:50000"
          client_id: "cluster-a-queue-connection"
          auth_token: ""
          channels: "queue.a,queue.b,queue.c"
          expiration_seconds: 0
          delay_seconds: 0
          max_receive_count: 3
          dead_letter_queue: "dead-letter.queue.a"
        - address: "kubemq-cluster-b-grpc.kubemq.svc.cluster.local:50000"
          client_id: "cluster-b-queue-connection"
          auth_token: ""
          channels: "queue.a,queue.b,queue.c"
          expiration_seconds: 0
          delay_seconds: 0
          max_receive_count: 3
          dead_letter_queue: "dead-letter.queue.b"
        - address: "kubemq-cluster-c-grpc.kubemq.svc.cluster.local:50000"
          client_id: "cluster-c-queue-connection"
          auth_token: ""
          channels: "queue.a,queue.b,queue.c"
          expiration_seconds: 0
          delay_seconds: 0
          max_receive_count: 3
          dead_letter_queue: "dead-letter.queue.c"

Last updated