A small addition for the component discovery: Flink works so that the
TaskManagers register at the JobManager. This means that the TaskManager
have to somehow retrieve the JobManager's address. Either you do it as
Philippe described it or you use the HA mode with ZooKeeper. In the latter
case, the
Weave allows encryption of the vpn, and your Flink containers can be secured
using kerberos
https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/config.html#kerberos-based-security.
> Le 24 mars 2017 à 11:16, Chakravarthy varaga a
> écrit :
>
> Hi,
>
> Thanks for your inpu
Hi,
Thanks for your inputs. It kind of makes sense to use a container
orchestrator to plough through networking under the hood.
How do you tackle security?
I don't see a way to authorize users for job management. I understand
few orchestrators provide name space isolation and secur
Hi,
If I can give my 2 cents.
One simple solution to your problem is using weave (https://www.weave.works/) a
Docker network plugin.
We’ve been working for more then year with dockerized
(Flink+zookeeper+Yarn+spark+Kafka+hadoop+elasticsearch ) cluster using weave.
Design your docker container
Hi,
I request someone to help here.
Best Regards
CVP
On Thu, Mar 23, 2017 at 10:13 PM, Chakravarthy varaga <
chakravarth...@gmail.com> wrote:
> I'm looking forward to hearing some updates on this...
>
> Any help here is highly appreciated !!
>
> On Thu, Mar 23, 2017 at 4:20 PM, Chakravarthy
I'm looking forward to hearing some updates on this...
Any help here is highly appreciated !!
On Thu, Mar 23, 2017 at 4:20 PM, Chakravarthy varaga <
chakravarth...@gmail.com> wrote:
> Hi Team,
>
> We are doing a PoC to deploy Flink cluster on AWS. All runtime
> components will be dockerized
