fix: update azure-vnet directory permissions #2819
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for Change:
Address race issue in 1.6.x
Now it should not matter if cni or k8s makes the directory since they should both have 0755 permissions.
Issue Fixed:
#2818
Requirements:
Notes:
Created nodesubnet/legacy cluster (no cns), checked var/run/azure-vnet directory and it has 0644 permissions.
Replaced cni version with this new one and restarted the node. The var/run/azure-vnet directory now has 0755 permissions after the reboot.