Red Hat Summit Red Hat SummitSupportoConsoleSviluppatoriInizia una provaContatti

Questo contenuto non è disponibile nella lingua selezionata.

Chapter 17. Azure Storage Queue Sink

Send Messages to Azure Storage queues.

Important

The Azure Storage Queue Sink Kamelet is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production.

These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview.

The Kamelet is able to understand the following headers to be set:

  • expiration / ce-expiration: as the time to live of the message in the queue.

If the header won’t be set the default of 7 days will be used.

The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S — parses as 20.345 seconds, P2D — parses as 2 days.

17.1. Configuration Options
Copia collegamento

The following table summarizes the configuration options available for the azure-storage-queue-sink Kamelet:

Expand
PropertyNameDescriptionTypeDefaultExample

accessKey *

Access Key

The Azure Storage Queue access Key.

string

  

accountName *

Account Name

The Azure Storage Queue account name.

string

  

queueName *

Queue Name

The Azure Storage Queue container name.

string

  
Note

Fields marked with an asterisk (*) are mandatory.

17.2. Dependencies
Copia collegamento

At runtime, the azure-storage-queue-sink Kamelet relies upon the presence of the following dependencies:

  • camel:azure-storage-queue
  • camel:kamelet

17.3. Usage
Copia collegamento

This section describes how you can use the azure-storage-queue-sink.

17.3.1. Knative Sink
Copia collegamento

You can use the azure-storage-queue-sink Kamelet as a Knative sink by binding it to a Knative object.

azure-storage-queue-sink-binding.yaml

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: azure-storage-queue-sink-binding
spec:
  source:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: azure-storage-queue-sink
    properties:
      accessKey: "The Access Key"
      accountName: "The Account Name"
      queueName: "The Queue Name"
Copy to Clipboard Toggle word wrap

17.3.1.1. Prerequisite
Copia collegamento

Make sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.

17.3.1.2. Procedure for using the cluster CLI
Copia collegamento

  1. Save the azure-storage-queue-sink-binding.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command: 

    oc apply -f azure-storage-queue-sink-binding.yaml
    Copy to Clipboard Toggle word wrap

17.3.1.3. Procedure for using the Kamel CLI
Copia collegamento

Configure and run the sink by using the following command: 

kamel bind channel:mychannel azure-storage-queue-sink -p "sink.accessKey=The Access Key" -p "sink.accountName=The Account Name" -p "sink.queueName=The Queue Name"
Copy to Clipboard Toggle word wrap

This command creates the KameletBinding in the current namespace on the cluster.

17.3.2. Kafka Sink
Copia collegamento

You can use the azure-storage-queue-sink Kamelet as a Kafka sink by binding it to a Kafka topic.

azure-storage-queue-sink-binding.yaml

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: azure-storage-queue-sink-binding
spec:
  source:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: azure-storage-queue-sink
    properties:
      accessKey: "The Access Key"
      accountName: "The Account Name"
      queueName: "The Queue Name"
Copy to Clipboard Toggle word wrap

17.3.2.1. Prerequisites
Copia collegamento

Ensure that you’ve installed the AMQ Streams operator in your OpenShift cluster and created a topic named my-topic in the current namespace. Make also sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.

17.3.2.2. Procedure for using the cluster CLI
Copia collegamento

  1. Save the azure-storage-queue-sink-binding.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command: 

    oc apply -f azure-storage-queue-sink-binding.yaml
    Copy to Clipboard Toggle word wrap

17.3.2.3. Procedure for using the Kamel CLI
Copia collegamento

Configure and run the sink by using the following command: 

kamel bind kafka.strimzi.io/v1beta1:KafkaTopic:my-topic azure-storage-queue-sink -p "sink.accessKey=The Access Key" -p "sink.accountName=The Account Name" -p "sink.queueName=The Queue Name"
Copy to Clipboard Toggle word wrap

This command creates the KameletBinding in the current namespace on the cluster.

17.4. Kamelet source file
Copia collegamento

https://github.com/openshift-integration/kamelet-catalog/azure-storage-queue-sink.kamelet.yaml

Torna in cima
Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Aiutiamo gli utenti Red Hat a innovarsi e raggiungere i propri obiettivi con i nostri prodotti e servizi grazie a contenuti di cui possono fidarsi. Esplora i nostri ultimi aggiornamenti.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Theme

© 2025 Red Hat