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 <[email protected]> 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 <[email protected]> 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 < >> [email protected]> 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/ >>> >>
