node exporter port conflict

[csabika7]

Helm chart for seldon-core-analytics includes installing a node-exporter daemonset. As it is directly uses the host network reserving the port 9100.
Deployment of this helm chart would then fail if node-exporeter have been deployed already for another application like ranch.

Do you know some way to still be able to install seldon-core-analytics which would use the already deployed node-exporter if it is already present?

[ukclivecox]

Would a fix me to make that port configurable in the Helm chart values? Could you submit a PR?

[csabika7]

Can you even do that?
In the Dockerfile of the node-exporter the 9100 port is exposed.
In the helm chart the hostNetwork is set to true.
This means in the node exporter template file I cannot set different values for the containerPort and the hostPort (e.g. containerPort: 9100, hostPort: 9101). However if I set a port other than 9100 for the containerPort then nothing will be exposed.

I could be done if hostNetwork is set to false I guess. Is there any reason for setting it to true?

[gsunner]

merged changes in PR #617