pick up a random port for metrics when MountPod using hostNetwork #586
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the MountPod can inherit some attributes from
juicefs-csi-node
daemonset:So if we make
juicefs-csi-node
to behostNetwork: true
, those MountPods will also behostNetwork: true
. What makes the problem is those metrics exported byjuicefs mount
if these MountPods listen at the same port.This PR makes these MountPods listen at a random port when they are in hostNetwork mode, and we also do not proclaim any container port.