Hi Roman,
Thanks for the information. I was able to get ignite working with RBAC
enabled K8s cluster.
The issue was with K8s calico networking, I had set it up wrongly because of
which I was getting errors.
Regards,
Vishwas
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Vishwas,
Where your kubernetes cluster is located? Google Cloud, Openshift or
somewhere else?
I've checked your service account configs (with role and binding) on Google
Cloud. It works well. Maybe the problem in your deployment file or in
changes related to docker image.
Here are the steps
Hi Roman,
Thanks for the response. I followed the steps you mentioned and also the
below link
https://stackoverflow.com/questions/50817940/failed-to-retrieve-ignite-pods-ip-addresses/50818842#50818842
apiVersion: v1
kind: ServiceAccount
metadata:
name: ignite
namespace: default
---
Hi Vishwas,
Usually, this issue happens because of:
1. Default service account doesn't have permissions to use the endpoint to
get all related IP addresses (of Ignite nodes).
2. A cluster is deployed in not default namespace. For example, in Openshift
namespace is a project name.
To resolve
Hi,
I am trying to bring up Ignite on RBAC enabled K8s cluster. As part of
discovery, when ignite nodes are trying to discover one another, I am seeing
below error:
[02:16:08,755][SEVERE][tcp-disco-ip-finder-cleaner-#4][TcpDiscoverySpi]
Failed to clean IP finder up.
class
