- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Monday, November 23, 2020 9:22:02 AM
> Subject: Re: Edge router on the client side
>
> On Mon, Nov 23, 2020 at 7:37 AM Petrenko, Vadim
> wrote:
>
> > Thank y
al Message-
> From: Chuck Rolke
> Sent: vrijdag 20 november 2020 17:57
> To: users@qpid.apache.org
> Subject: Re: Edge router on the client side
>
> Also, do not build the image with certificates embedded within it.
> Find a way to inject the connection secrets into the
ount of routing information that needs to be exchanged between the
edge and its interior is minimal and probably is not something to be
concerned about.
-K
> Thank you.
>
> -Original Message-
> From: Chuck Rolke
> Sent: vrijdag 20 november 2020 17:57
> To: users@qpid
0 17:57
To: users@qpid.apache.org
Subject: Re: Edge router on the client side
Also, do not build the image with certificates embedded within it.
Find a way to inject the connection secrets into the container as it is
launched.
- Original Message -
> From: "Ted Ross"
> To: us
> Subject: Re: Edge router on the client side
>
> On Fri, Nov 20, 2020 at 5:32 AM Petrenko, Vadim
> wrote:
>
> > Hi Qpid developers,
> >
> > We’re considering this possibility:
> >
> > Containerize a preconfigured Edge router (possibly together w
On Fri, Nov 20, 2020 at 5:32 AM Petrenko, Vadim
wrote:
> Hi Qpid developers,
>
> We’re considering this possibility:
>
> Containerize a preconfigured Edge router (possibly together with Artemis)
> and give it to an application team.
>
> The application team will then deploy this container in thei
Hi Qpid developers,
We’re considering this possibility:
Containerize a preconfigured Edge router (possibly together with Artemis) and
give it to an application team.
The application team will then deploy this container in their environment ->
the Edge router will connect to a couple Interior r
