You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexandr Shapkin (Jira)" <ji...@apache.org> on 2022/06/22 13:08:00 UTC
[jira] [Commented] (IGNITE-17147) Ignite should not talk to kubernetes default service to get its own IP
[ https://issues.apache.org/jira/browse/IGNITE-17147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557442#comment-17557442 ]
Alexandr Shapkin commented on IGNITE-17147:
-------------------------------------------
[~laptimus] Could you please elaborate on this task?
What's you improvement suggestion?
Am I right that you are referring to this configuration: [https://www.gridgain.com/sdk/latest/javadoc/org/apache/ignite/kubernetes/configuration/KubernetesConnectionConfiguration.html#setMasterUrl-java.lang.String-]
and its default value - 'https://kubernetes.default.svc.cluster.local:443'?
> 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)