Hello,
Camel is a very flexible framework. You may choose plenty of technologies
to expose your service to the outer world. Probably in today's standards
you can expose a REST endpoint and send the list of files over that
endpoint triggering the logic when a user makes a call to the rest service.
When deploying on Kubernetes via Camel K, you should automatically have a
Service resource which would expose the Integration and your REST
endpoints. At that stage your external microservice can call such a
Kubernetes Service to get the information required.

Hope that helps,
Pasquale.

On Tue, Jan 21, 2025 at 4:44 PM Sanin Palikuca
<sanin.palik...@qss.ba.invalid> wrote:

> Hi,
>
>
>
> I have a request to create an Apache Camel K Pipe/Integration that
> pulls/sends data from and to Minio, i.e., retrieves and uploads files to a
> specific Minio bucket. I have created the Pipe/Integration YAML file, and I
> can see that it successfully logs the files from the Minio bucket.
>
> What I need now is to call this Pipe/Integration from my external .NET
> microservice in order to get the list of all files in the bucket. The
> process would go like this: the .NET microservice calls the Camel K
> Pipe/Integration, and it returns the list of files from the bucket to the
> .NET service.
>
> Note that I am doing this on OpenShift.
>
>
>
> Please assist me on how to expose the created Pipe/Integration so it can
> be called from the .NET service — if this is indeed possible.
>
>
>
> Pozdrav/Regards,
>
>
> ------------------------------------------------------------------------------------------------
>
> [image: cid:image003.png@01D610ED.0F408AF0]
>
> *Sanin Paliku**ća*
>
> Head of Enginering and Cloud
>
> *QSS *d.o.o.
> Branilaca Sarajeva 20/III
> 71000 Sarajevo
> Bosnia and Herzegovina
>
> t: +387 33 *563 000*
>
> m:+387 61 *712 805*
>
>
> www.qss.ba
>
>
>
> [image: cid:image002.png@01D84B31.62E81FD0]
> <https://qss.ba/resources/qss-endpoint-protection>
>
>
>
> Klasifikacija poruke: "OGRANIČENO".
>
> Izjava o odricanju prava: Informacije sadržane u ovoj poruci mogu biti
> privilegovane, povjerljive ili zaštićene od razotkrivanja. Ukoliko Vam ova
> poruka nije namijenjena ili niste zaposlenik ili posrednik odgovoran za
> dostavljanje ove poruke namijenjenom primaocu, ovim Vas obaviještavamo da
> svako širenje, distribuiranje ili kopiranje ove komunikacije je izričito
> zabranjeno. Ukoliko ste dobili greškom ovu poruku, molimo Vas da nas
> obavijestite odmah odgovorom na ovu poruku i brisanjem ove poruke sa Vašeg
> računara.
>
> Classification of the messages: "RESTRICTED".
> Disclaimer: The information contained in this message may be privileged,
> confidential and protected from disclosure. If the reader of this message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby notified
> that any dissemination, distribution or copying of this communication is
> strictly prohibited. If you have received this communication in error,
> please notify us immediately by replying to this message and deleting it
> from your computer.
> ---
> Message scanned by Cisco IronPort Mail Security Appliance
>

Reply via email to