-
Notifications
You must be signed in to change notification settings - Fork 179
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
Use identical file system for node tuning and keep symlinks working #2033
Use identical file system for node tuning and keep symlinks working #2033
Conversation
fee7c30
to
aca7a12
Compare
aca7a12
to
f97d359
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/assign rzetelskik
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rzetelskik, tnozicka, zimnx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description of your changes:
When the Kubernetes node file system contains top level symlinks our node setup fails to resolve them in the chroot. This is because we skip bind mounting some directories, like
/var
and other top level dirs can be symlinks pointing there. (This is a majority of top level dirs on Core OS and immutable filesystems.)To keep top level symlinks for node setup working we need to create an identical filesystem structure. This will also clean up the overrides we have.
Which issue is resolved by this Pull Request:
Resolves #2029