-
Notifications
You must be signed in to change notification settings - Fork 4
Frequently Asked Questions
Ramesh Polishetti edited this page Oct 17, 2024
·
4 revisions
- SPI communication exception between EC2 nodes provisioned using AMS
- Ignite clustering not working on Rancher Kubernetes
- You may observe SPI communication exception between BE Ignite nodes deployed on EC2 boxes provisioned using Amazon Managed Service (AMS).
- Solution: Remove short name aliases (if any) from /etc/hosts file for the loopback IP entry i.e 127.0.0.1
If node is not able to join the cluster try adding below annotations to the deployments:
traffic.sidecar.istio.io/excludeInboundPorts: "47100,47500"
traffic.sidecar.istio.io/excludeOutboundPorts: "47100,47500"