Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
References: <38BAD428-A61C-4CD1-9EE8-133EFBAB6167@gridgain.com> <CA+0=VoX8mUygE44Js4=yMXTPeZNjuzTvqgBa0ifyJcSf4e-QqA@mail.gmail.com>
In-Reply-To: <CA+0=VoX8mUygE44Js4=yMXTPeZNjuzTvqgBa0ifyJcSf4e-QqA@mail.gmail.com>
From: Paulo Pires <pires@littlebits.cc>
Date: Tue, 28 Jun 2016 18:43:10 +0000
Message-ID: <CAO8YOYV3NuvUx=UNATqwRk8E0TzYZh6pu+jrEOUCR+=95i5LKQ@mail.gmail.com>
Subject: Re: Ignite & Kubernetes
To: user@ignite.apache.org, dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a1143dd0ac3fa0505365b0257
archived-at: Tue, 28 Jun 2016 19:16:08 -0000

--001a1143dd0ac3fa0505365b0257
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I came up with https://github.com/pires/apache-ignite-discovery-kubernetes.

I have been using this in production Kubernetes. Obviously, one needs DNS
integration which happens to be a best-practice anyway.

Pires

On Thu, Apr 28, 2016 at 4:45 PM Dmitriy Setrakyan <dsetrakyan@apache.org>
wrote:

> Ignite does not have any specific Kubernetes integration, however, if it
> supports TCP/IP, which I am pretty sure it does, then we can easily do
> auto-discovery there using our static IP discovery:
>
>
> https://apacheignite.readme.io/docs/cluster-config#static-ip-based-discov=
ery
>
> Also, it is likely that it will work smoothly with Ignite docker containe=
r:
> https://ignite.apache.org/download.cgi#docker
>
> D.
>
> On Thu, Apr 28, 2016 at 6:50 AM, Christos Erotocritou <
> christos@gridgain.com> wrote:
>
>> Hi all,
>>
>> Is anyone working with Ignite & kubernetes?
>>
>> Moreover I=E2=80=99d like to understand how it would be possible to do a=
uto
>> discovery of new Ignite nodes.
>>
>> Thanks,
>>
>> Christos
>
>
>

--001a1143dd0ac3fa0505365b0257--