set file system permission via yurtadm to default

[fujitatomoya]

What type of PR is this?

/kind bug

address #1573

What this PR does / why we need it:

It does use the default file access permission.

• /opt/cni/bin

tomoyafujita@~ >ls -lt /opt/cni/
total 4.0K
drwxr-xr-x 2 root root 4.0K Jun  9 15:43 bin/

• /etc/systemd/system/kubelet.service.d/10-kubeadm.conf

tomoyafujita@~ >ls -lt /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
-rw-r----- 1 root root 898 Sep 21  2022 /etc/systemd/system/kubelet.service.d/10-kubeadm.conf

Which issue(s) this PR fixes:

Fixes #1573

Special notes for your reviewer:

• I believe this makes sense, and avoid unexpected problem such as Unable to install Cilium: timeout while waiting for status to become successful cilium/cilium#22933
• Since we found this issue based on v1.1.0, current target to set so. I am happy to address master if you guys want me to do so, then we can backport the fix for each release.

[openyurt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fujitatomoya
To complete the pull request process, please assign yixingjia
You can assign the PR to them by writing /assign @yixingjia in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[fujitatomoya]

I think same fixes can be applied to master branch as well. if we should fix that on master branch and backporting the fix for each release, that i can help with.

[YTGhost]

I think same fixes can be applied to master branch as well. if we should fix that on master branch and backporting the fix for each release, that i can help with.

Yes, we should fix that on master branch and backporting the fix for each release. And maybe you should submit the PR to the master branch, and then after merge we can have github-action automatically backport it via the backport command

[fujitatomoya]

@YTGhost okay that is what i though.

my concern was that backport would not be straight-forward since there is huge difference between master and v1.1.0.

anyway, i understand the procedure, fix will be resubmitted targeted to master branch.

[fujitatomoya]

@YTGhost i will go ahead to close this one since i created the replacement #1576 targeted to master branch.