[
https://issues.apache.org/jira/browse/IGNITE-17147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557493#comment-17557493
]
laptimus commented on IGNITE-17147:
---
Ignite needs to know its IP address and in Kubernetes environment, its doing it
by contacting [https://kubernetes.default.svc.cluster.local:443.] But in our
kubernetes cluster we have calico network policy implemented that is preventing
Ignite to talk to [https://kubernetes.default.svc.cluster.local:443.]
There should be an alternate way for Ignite to know its own IP address in
kubernetes environment.
thanks
> Ignite should not talk to kubernetes default service to get its own IP
> --
>
> Key: IGNITE-17147
> URL: https://issues.apache.org/jira/browse/IGNITE-17147
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.11.1
> Environment: Kubernetes
>Reporter: laptimus
>Priority: Major
>
> Ignite should not talk to kubernetes default service to get its own IP
> We have kubernetes cluster with calico network policies and seems like ignite
> is the only application in our cluster that needs access to kubernetes
> default service
> I see this as a security risk
> Please implement an alternative way in IP Finder as that the class that talks
> to kubernetes default service to know pod IP address
>
> thanks
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
