You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by jose farfan <jo...@gmail.com> on 2020/07/28 11:50:15 UTC
Re: Kubernetes : Connection timed out (Connection timed out)
Hi
I have similar problem.
For some reason this host are not resolve
"kubernetes.default.svc.cluster.local".
I am still investigating the reason.
But in my case "kubernetes.default" was resolved, then
I have added the masterUrl in the config file
(I added directly the ip: <property
name="masterUrl" value="https://172.22.100.9:6443"/> " of Master API.
<!--
> Configuration example with Kubernetes IP finder enabled.
> -->
> <beans xmlns="http://www.springframework.org/schema/beans"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd">
>
> <bean class="org.apache.ignite.configuration.IgniteConfiguration">
>
> <!-- Enabling Apache Ignite Persistent Store. -->
> <property name="dataStorageConfiguration">
> <bean
> class="org.apache.ignite.configuration.DataStorageConfiguration">
> <property name="defaultDataRegionConfiguration">
> <bean
> class="org.apache.ignite.configuration.DataRegionConfiguration">
> <property name="persistenceEnabled" value="true"/>
> </bean>
> </property>
> </bean>
> </property>
>
> <!-- Explicitly configure TCP discovery SPI to provide list of
> initial nodes. -->
> <property name="discoverySpi">
> <bean
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> <property name="ipFinder">
> <!--
> Enables Kubernetes IP finder and setting custom
> namespace and service names.
> -->
> <bean
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder">
> <property name="namespace" value="development"/>
> <property name="serviceName" value="ignite"/>
> <property name="masterUrl" value="
> https://172.22.100.9:6443"/>
> </bean>
> </property>
> </bean>
> </property>
> </bean>
> </beans>
>
You need to find your master api address.
On Tue, 28 Jul 2020 at 13:19, steve.hostettler <st...@gmail.com>
wrote:
> Hello,
>
> making some progress
> I added the missing
>
> hostNetwork: true
>
> and now I get
>
> Caused by: java.net.UnknownHostException:
> kubernetes.default.svc.cluster.local
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by "steve.hostettler" <st...@gmail.com>.
Hello Denis,
same code, same config, today it works so it was an transient AKS thing. no
idea what
Best Regards
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by Denis Magda <dm...@apache.org>.
Steve,
Excellent, glad the problem is gone. The community is working on the new
documentation and, as far as I know, the Kubernetes instructions will be
brought up-to-date. Thanks for pointing that out.
-
Denis
On Wed, Jul 29, 2020 at 2:53 AM steve.hostettler <st...@gmail.com>
wrote:
> Hello Dennis,
>
> so it works again, it was apparently a transient Azure problem when
> creating
> new clusters.
> FYI the documentation and
> https://github.com/apache/ignite/tree/master/modules/kubernetes/config/az
> is not up to date and gave errors when executing them (from a K8S
> perspective)
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by "steve.hostettler" <st...@gmail.com>.
Hello Dennis,
so it works again, it was apparently a transient Azure problem when creating
new clusters.
FYI the documentation and
https://github.com/apache/ignite/tree/master/modules/kubernetes/config/az
is not up to date and gave errors when executing them (from a K8S
perspective)
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by Denis Magda <dm...@apache.org>.
Steve, Jose,
Try to follow this instruction created specifically for Azure Kubernetes
Service (AKS):
https://www.gridgain.com/docs/latest/installation-guide/kubernetes/azure-deployment
Not, if the cluster (server nodes) are planned to be deployed as virtual
machines (on-premises) while the thick clients will be running in AKS then
keep this configuration option in mind (it's already supported by GridGain
and will be available in Ignite 2.9):
https://www.gridgain.com/docs/latest/developers-guide/clustering/running-client-nodes-behind-nat
-
Denis
On Tue, Jul 28, 2020 at 12:03 PM jose farfan <jo...@gmail.com> wrote:
> Hi
>
> Also I am using this file ignite-rbac.yaml. Maybe can help you,..
> I am still learning how to deploy ignite in the cluster.
>
> BR
> Jose
>
>
> On Tue, 28 Jul 2020 at 20:53, jose farfan <jo...@gmail.com> wrote:
>
>> Hi Steve
>>
>> No, I am using a on-premise cluster.
>>
>> can you access a pod using the shell, and try to ping
>> kubernetes.default.svc.cluster.local.
>>
>> BR
>> Jose
>>
>>
>>
>> On Tue, 28 Jul 2020 at 16:05, steve.hostettler <
>> steve.hostettler@gmail.com> wrote:
>>
>>> Running
>>>
>>> curl --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt -H
>>> "Authorization: Bearer $(cat
>>> /var/run/secrets/kubernetes.io/serviceaccount/token)" -H "Acept:
>>> application/json"
>>>
>>> https://kubernetes.default.svc.cluster.local:443/api/v1/namespaces/default/endpoints/processing-engine-pe-v1-ignite
>>>
>>> On my local K8S works but not on Azure. On Azure I end up with a Timeout.
>>>
>>> Any Idea?
>>>
>>>
>>>
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>
>>
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by jose farfan <jo...@gmail.com>.
Hi
Also I am using this file ignite-rbac.yaml. Maybe can help you,..
I am still learning how to deploy ignite in the cluster.
BR
Jose
On Tue, 28 Jul 2020 at 20:53, jose farfan <jo...@gmail.com> wrote:
> Hi Steve
>
> No, I am using a on-premise cluster.
>
> can you access a pod using the shell, and try to ping
> kubernetes.default.svc.cluster.local.
>
> BR
> Jose
>
>
>
> On Tue, 28 Jul 2020 at 16:05, steve.hostettler <st...@gmail.com>
> wrote:
>
>> Running
>>
>> curl --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt -H
>> "Authorization: Bearer $(cat
>> /var/run/secrets/kubernetes.io/serviceaccount/token)" -H "Acept:
>> application/json"
>>
>> https://kubernetes.default.svc.cluster.local:443/api/v1/namespaces/default/endpoints/processing-engine-pe-v1-ignite
>>
>> On my local K8S works but not on Azure. On Azure I end up with a Timeout.
>>
>> Any Idea?
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by jose farfan <jo...@gmail.com>.
Hi Steve
No, I am using a on-premise cluster.
can you access a pod using the shell, and try to ping
kubernetes.default.svc.cluster.local.
BR
Jose
On Tue, 28 Jul 2020 at 16:05, steve.hostettler <st...@gmail.com>
wrote:
> Running
>
> curl --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt -H
> "Authorization: Bearer $(cat
> /var/run/secrets/kubernetes.io/serviceaccount/token)" -H "Acept:
> application/json"
>
> https://kubernetes.default.svc.cluster.local:443/api/v1/namespaces/default/endpoints/processing-engine-pe-v1-ignite
>
> On my local K8S works but not on Azure. On Azure I end up with a Timeout.
>
> Any Idea?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by "steve.hostettler" <st...@gmail.com>.
Running
curl --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt -H
"Authorization: Bearer $(cat
/var/run/secrets/kubernetes.io/serviceaccount/token)" -H "Acept:
application/json"
https://kubernetes.default.svc.cluster.local:443/api/v1/namespaces/default/endpoints/processing-engine-pe-v1-ignite
On my local K8S works but not on Azure. On Azure I end up with a Timeout.
Any Idea?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by "steve.hostettler" <st...@gmail.com>.
So it appears that since this morning I am not able to access the cluster
from within a pod in Azure. Very very strange
/ # wget http://kubernetes.default.svc.cluster.local:443/api
Connecting to kubernetes.default.svc.cluster.local:443 (10.0.0.1)
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Kubernetes : Connection timed out (Connection timed out)
Posted by "steve.hostettler" <st...@gmail.com>.
Hello Jose,
thanks for the answer. Are you on azure as well by any chance?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/