Re: Configuring TcpDiscoveryKubernetesIpFinder
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 the default of 'ignite'. Thanks. On 9/11/18, 2:16 PM, "vkulichenko" wrote: Jeff, Ignite configuration is an XML file which can be quite large. What is the reason for the requirement to specify it inline? -Val -- Sent from: https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_&d=DwICAg&c=ObqWq9831a7badpzAhIKIA&r=GDHaUsXuW5l_tQf8Lb0qSFuKsPCA5WAkjY2k5nQo7uw&m=W_muUks4YGxaoiZ6r0C4g2gTNOBUu1wWS9wusKu-_KU&s=iQ37DHrn47rZ4p7sSUkD4vYR5FkNczM7Ilh2lm_zGlY&e= This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
Configuring TcpDiscoveryKubernetesIpFinder
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: CONFIG_URI value: https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-persistence.xml This is not going to work for us. Is there another option for specifying this config? We would like to be able to supply this config inline, in the k8s 'deployment' spec.containers.env. Specifically, we need to set serviceName. The default 'ignite' is not a good choice. Thanks, Jeff This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
Re: Error installing Ignite on K8s
Hi Denis, Yes, all of our apps reside in k8s, so there would be no need for external access. Thanks for the info! Jeff From: Denis Magda Reply-To: "user@ignite.apache.org" Date: Tuesday, September 11, 2018 at 8:30 AM To: "user@ignite.apache.org" Subject: Re: Error installing Ignite on K8s Jeff, The sessionAffinity is needed only if you plan to access Ignite cluster deployed in K8 from an application deployed outside of it. For instance, it will ensure that a remote JDBC session will stick to a specific Ignite pod. However, if all your applications are deployed 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 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 caching? I'm guessing the answer would be 'no, it's not required.' Thanks, Jeff On 9/10/18, 4:15 PM, "vkulichenko" mailto:valentin.kuliche...@gmail.com>> wrote: Does it work without specifying sessionAffinity? -Val -- Sent from: https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_&d=DwICAg&c=ObqWq9831a7badpzAhIKIA&r=GDHaUsXuW5l_tQf8Lb0qSFuKsPCA5WAkjY2k5nQo7uw&m=nGR_kKy4EMqQjzu9FfD9BViiBYvvkZabdxLvh7lXjYw&s=Z-AZJ1xOOCKZyUNQNOndPrBGu7rnXR0zTXTyOSUwNbM&e= This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately. This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
Re: Error installing Ignite on K8s
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 caching? I'm guessing the answer would be 'no, it's not required.' Thanks, Jeff On 9/10/18, 4:15 PM, "vkulichenko" wrote: Does it work without specifying sessionAffinity? -Val -- Sent from: https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_&d=DwICAg&c=ObqWq9831a7badpzAhIKIA&r=GDHaUsXuW5l_tQf8Lb0qSFuKsPCA5WAkjY2k5nQo7uw&m=nGR_kKy4EMqQjzu9FfD9BViiBYvvkZabdxLvh7lXjYw&s=Z-AZJ1xOOCKZyUNQNOndPrBGu7rnXR0zTXTyOSUwNbM&e= This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
Error installing Ignite on K8s
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: ClientIP" What is a valid value for sessionAffinity that works with Ignite? Is sessionAffinity required? Thanks. // Service spec (from https://apacheignite.readme.io/docs/ignite-service) // This is supposed to be a guide for k8s, but it doesn't work. // Could be that there's an issue with creating service on AWS? apiVersion: v1 kind: Service metadata: # The name must be equal to TcpDiscoveryKubernetesIpFinder.serviceName name: ignite # The name must be equal to TcpDiscoveryKubernetesIpFinder.namespaceName namespace: ignite spec: type: LoadBalancer ports: - name: rest port: 8080 targetPort: 8080 - name: sql port: 10800 targetPort: 10800 - name: thinclients port: 10900 targetPort: 10900 sessionAffinity: ClientIP selector: # Must be equal to the label set for Ignite pods. app: ignite This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
