We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have a symlink from /etc/kubernetes/manifests to a manifest on the volume, to avoid the race in #73.
But once the mount the volume, it is possible that a different manifest exists, and the symlink then resolves.
It would be safer to delete the symlink before mounting the volume. Another option would be to use a UUID in the mount path.
I'm not sure this actually matters much, because the manifest shouldn't be changing anyway. But we should probably fix to prevent future issues.
The text was updated successfully, but these errors were encountered:
Should we bump this again or just close it? Seems to not be causing issues.
Sorry, something went wrong.
Closing
No branches or pull requests
We have a symlink from /etc/kubernetes/manifests to a manifest on the volume, to avoid the race in #73.
But once the mount the volume, it is possible that a different manifest exists, and the symlink then resolves.
It would be safer to delete the symlink before mounting the volume. Another option would be to use a UUID in the mount path.
I'm not sure this actually matters much, because the manifest shouldn't be changing anyway. But we should probably fix to prevent future issues.
The text was updated successfully, but these errors were encountered: