Re: Thin Client Kubernetes discovery

Max, There is no point in using DNS names instead of IP addresses if an application developer stills needs to set the latter in a thin client configuration. The developer should just pass a single parameter, start the client and forget about the connectivity matters. The state of the cluster will

Re: Thin Client Kubernetes discovery

Hi, StatefulSet provides predictable naming, then it should be easy to configure a client with addresses ignite-1,ignite-2...ignite-N. So there is no need in custom discovery, IPs etc. I think it corresponds to k8s patterns, as some pods are different from others as they store specific partitions (

Re: Thin Client Kubernetes discovery

Vladimir, I agree with you, StatefulSet is not related here. > it's not a strict rule to communicate only directly with a pod > running a node with a primary partition Yes, if a node with a primary partition is not known or can't be contacted, we fail over to a default (random) node (afaik this i

Re: Thin Client Kubernetes discovery

Hi guys, Maybe I'm missing something but I don't undestand how StatefulSet relates to the described functionality. StatefulSet is more about persistence. Correct me if I'm wrong but my current understanding is that we don't need to have any explicit state for a thin client connection. I'd like thi

Re: Thin Client Kubernetes discovery

Max, The point of Thin Client k8s discovery feature is to make k8s deployment simple - similar to KubernetesIPFinder for thick clients and servers. - I don't think that enabling partition awareness is related to a StatefulSet in any way - Not everyone is able to / wants to define a StatefulSet -

Re: Thin Client Kubernetes discovery

In case of an enabled partition-awareness feature or sessions I suppose that a state appears. And as we have a state we should use the stateful deployment of kubernetes with StatefulSet [1]. In that case addresses of nodes are predictable and aren't changed so one can configure a client with them.

Re: Thin Client Kubernetes discovery

Max, Denis, Partition Awareness [1] is our main reason to have a specialized k8s discovery mechanism in Thin Clients. k8s ingress mechanism is fine for a single client connection, but in Partition Aware mode thin clients need to connect to every server node, and track nodes as they enter or leave

Re: Thin Client Kubernetes discovery

We're discussing the case when the thin client and server nodes are a part of a single Kubernetes cluster. Ignite thick client uses KubernetesIPFinder to auto-discover other Ignite pods. The IP finder gets IP addresses of other Ignite pods

Re: Thin Client Kubernetes discovery

I'm not sure what you mean by inside/outside of kubernetes. Service name is visible within k8s environment. I've described a case with connection from another pod that is part of k8s cluster. To provide connection outside of Kubernetes one should configure Ingress [1]. It will have a fixed address

Re: Thin Client Kubernetes discovery

Max, That improvement automates the cluster discovery if both the cluster and thin clients are deployed *inside* of Kubernetes. That's my reading of the ticket's description. While you're referring to the case when the client is deployed outside of a K8S environment. @Vladimir Pligin , could you

Thin Client Kubernetes discovery

Hi, Igniters I'm now discovering the issue https://issues.apache.org/jira/browse/IGNITE-13204 and wondering what is a case that requires a client to be able to discover a cluster? I believe that discovery is a goal of kubernetes itself. We could assign a DNS name for a Service [1] and then any re

[jira] [Created] (IGNITE-13204) Java Thin client Kubernetes discovery

Alexandr created IGNITE-13204: - Summary: Java Thin client Kubernetes discovery Key: IGNITE-13204 URL: https://issues.apache.org/jira/browse/IGNITE-13204 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-13011) .NET: Thin client Kubernetes discovery

Pavel Tupitsyn created IGNITE-13011: --- Summary: .NET: Thin client Kubernetes discovery Key: IGNITE-13011 URL: https://issues.apache.org/jira/browse/IGNITE-13011 Project: Ignite Issue Type