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

NFS v4 VolumeMount Issue #943

Open
LaurinStreng opened this issue Jan 13, 2025 · 0 comments
Open

NFS v4 VolumeMount Issue #943

LaurinStreng opened this issue Jan 13, 2025 · 0 comments

Comments

@LaurinStreng
Copy link

Setup:

  • Kubernetes
  • Wazuh Version 4.9.2
  • CSI Driver: csi-driver-nfs Version: v4.9.0
  • Mounted NFS v4.2

Issue:
CrashLoopBackOff when initializing the Master or Worker Nodes.
Because in wazuh master/worker init they want to chown to root:wazuh or 0:999 on etc/filebeat and some other files.

But the NFS is configured with root squash, so all files are owned by nobody:nobody or 65534:65534
And cannot be owned by root.

Same Issue #556 but they closed it by using nfs3 or non_root squash

non_root squash would be a security issue, see therefor (https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/4/html/security_guide/s2-server-nfs-noroot)

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