Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-29 Thread Denis Magda
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 wrote: > Hello Dennis, > > so it

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-29 Thread steve.hostettler
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 fro

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-29 Thread steve.hostettler
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)

2020-07-28 Thread Denis Magda
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

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-28 Thread jose farfan
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 wrote: > Hi Steve > > No, I am using a on-premise cluster. > > can you access a pod using the shell, and try to ping

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-28 Thread jose farfan
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 wrote: > Running > > curl --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt -H > "Aut

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-28 Thread steve.hostettler
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

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-28 Thread steve.hostettler
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.x

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-28 Thread steve.hostettler
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/

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-28 Thread jose farfan
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:

Re: Kubernetes : Connection timed out (Connection timed out)

2020-07-28 Thread steve.hostettler
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/

Kubernetes : Connection timed out (Connection timed out)

2020-07-28 Thread steve.hostettler
Hello, Since this morning I get a strange Timeout on the connection to the cluster even with only one node. It used to work just fine until yesterday evening. At that point I destroyed the clustered and recreated it this morning. I do so with a batch so it is supposed to be the same all the time.