Minio Sink
Provided by: "Apache Software Foundation"
Upload data to Minio.
The Kamelet expects the following headers to be set:
-
file
/ce-file
: as the file name to upload
If the header won’t be set the exchange ID will be used as file name.
Configuration Options
The following table summarizes the configuration options available for the minio-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
accessKey * | Access Key | The access key obtained from Minio | string | ||
bucketName * | Bucket Name | The Minio Bucket name | string | ||
endpoint * | Endpoint | The Minio Endpoint, it can be an URL, domain name, IPv4 address or IPv6 address. | string |
| |
secretKey * | Secret Key | The secret key obtained from Minio | string | ||
autoCreateBucket | Autocreate bucket | Setting the autocreation of the S3 bucket bucketName. | boolean |
|
Fields marked with (*) are mandatory. |
Usage
This section summarizes how the minio-sink
can be used in various contexts.
Knative Sink
The minio-sink
Kamelet can be used as Knative sink by binding it to a Knative object.
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: minio-sink-binding
spec:
source:
ref:
kind: InMemoryChannel
apiVersion: messaging.knative.dev/v1
name: mychannel
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: minio-sink
properties:
accessKey: "The Access Key"
bucketName: "The Bucket Name"
endpoint: "http://localhost:9000"
secretKey: "The Secret Key"
Make sure you have Camel K installed into the Kubernetes cluster you’re connected to.
Save the minio-sink-binding.yaml
file into your hard drive, then configure it according to your needs.
You can run the sink using the following command:
kubectl apply -f minio-sink-binding.yaml