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_=DwICAg=ObqWq9831a7badpzAhIKIA=GDHaUsXuW5l_tQf8Lb0qSFuKsPCA5WAkjY2k5nQo7uw=W_muUks4YGxaoiZ6r0C4g2gTNOBUu1wWS9wusKu-_KU=iQ37DHrn47rZ4p7sSUkD4vYR5FkNczM7Ilh2lm_zGlY= 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: Configuring TcpDiscoveryKubernetesIpFinder
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: http://apache-ignite-users.70518.x6.nabble.com/
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.
