-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow disabling hostNetwork: true #274
Comments
Yes. I want to make it possible top set It would allow to decrease amount of opened ports on node IP. As far as I understood the only use-case for open ports is metrics collection and prometheus agent in k8s is able to collect the metrics using pod IP. So my point of view, is that such change would allow users to minimize potential attack surface for clusters with public IPs on nodes, without affecting any features. |
@Abhinandan-Purkait Do you really need to connect this POD to host network? If so why? |
+1 on this request. This pod has a couple of configurations that when put together can lead to a risky container:
|
Ping? |
Hi @dm3ch , Closing this as we have allowed users to disable hotNetwork |
Describe the problem/challenge you have
Reduce amount of open ports on k8s nodes.
As far as I understood the only port is exposed is 9500 and used only for metrics.
So it seems it's possible to collect it using pod or service scrapper.
Describe the solution you'd like
Helm value that would allow to disable
hostNetwork: false
For such case it would also useful to allow modify pod and service annotations throw chart values
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: