Skip to content
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

Microsoft recommendations to improve security and resilience in the Node Exporter service #3125

Open
sairinraychoudhury opened this issue Sep 18, 2024 · 0 comments

Comments

@sairinraychoudhury
Copy link

Needed advice from community members. We have deployed Promotheus node-exporter 1.8.2 using helm in Microsoft Azure Kubernetes Service (AKS). Also during an assessment of our platform towards improved security & resilience angle received below recommendations from Microsoft experts to be implemented.

    1. Containers sharing sensitive host namespaces should be avoided
    1. Usage of host networking and ports should be restricted
    1. Usage of pod HostPath volume mounts should be restricted to a known list to restrict node access from compromised containers
    1. The root access inside the service container should be avoided.

We are not sure if above actions when implemented will have an impact on Promotheus node-exporter since we used default Promotheus node-exporter configs which are in helm chart for Promotheus node-exporter.
Could anyone from the community please help or guide us on below queries?

  1. Have you tried implementing custom configs apart from default configs provided?
  2. Do you have a view of the impact by any means if we go ahead and implement this?
  3. Are there any other general recommendation towards achieving this?
@sairinraychoudhury sairinraychoudhury changed the title Microsoft recommendations to improve security and resilience Microsoft recommendations to improve security and resilience in the Node Exporter service Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant