Hi Val,
Ok, for smaller files inline is much cleaner, and that's what we prefer. But I
agree, for larger files its not such a good idea. Wew would really like to
avoid having configuration spread out all over the place.
Really, all we need to do is set the service name...we don't want to use
Hi,
I'm using the guide at https://apacheignite.readme.io/docs/stateless-deployment
to get an ignite instance running. Per that document, to configure
TcpDiscoveryKubernetesIpFinder you need to create a spring config file, and
then point to it using the CONFIG_URI env var.
- name:
ployed in K8 as well then you can
freely disregard sessionAffinity parameter. Is this your case?
--
Denis
On Tue, Sep 11, 2018 at 10:16 AM Jeff Simon
mailto:jeffsi...@fico.com>> wrote:
Yes if I remove session affinity it works. So my question is does ignite
require sessionAffinity? And to
Yes if I remove session affinity it works. So my question is does ignite
require sessionAffinity? And to be honest, I'm not really sure what we are
using ignite for since it seems to be a multi-purpose app. I think we are
going to use for caching. So would session affinity be required for
Hi, trying to install ignite on k8s running on ec2. K8s cluster is running on
EC2 in AWS (not using EKS.)
Following the guide at https://apacheignite.readme.io/docs/stateless-deployment
Getting the following error when trying to create the k8s service:
"unsupported load balancer affinity:
