Remove the execute permission from the directory

[zishen]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Reduce permissions for directories created by karmada itself.
From 755 to 700. Prevent unauthorized users from modifying content.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

@RainbowMango @whitewindmills @XiShanYongYe-Chang

[RainbowMango]

CI is failing:
https://github.com/karmada-io/karmada/actions/runs/5961906734/job/16172031967?pr=3992

I0824 09:28:14.555201   18831 deploy.go:184] kubeconfig file: /home/runner/.kube/karmada-host.config, kubernetes: https://172.18.0.5:6443/
I0824 09:28:14.63[56](https://github.com/karmada-io/karmada/actions/runs/5961906734/job/16172031967?pr=3992#step:5:57)89   18831 deploy.go:204] karmada apiserver ip: [172.18.0.5]
error: certificate generation failed.unable to write private key to file mkdir /home/runner/karmada/pki: permission denied

[zishen]

CI is failing: https://github.com/karmada-io/karmada/actions/runs/5961906734/job/16172031967?pr=3992

I0824 09:28:14.555201   18831 deploy.go:184] kubeconfig file: /home/runner/.kube/karmada-host.config, kubernetes: https://172.18.0.5:6443/
I0824 09:28:14.63[56](https://github.com/karmada-io/karmada/actions/runs/5961906734/job/16172031967?pr=3992#step:5:57)89   18831 deploy.go:204] karmada apiserver ip: [172.18.0.5]
error: certificate generation failed.unable to write private key to file mkdir /home/runner/karmada/pki: permission denied

yea, Directory requires execute permission, otherwise files cannot be created.
so, I changed the permission to 700.

[chaosi-zju]

runner@fv-az454-559:~$ pwd
/home/runner
runner@fv-az454-559:~$ mkdir /home/runner/karmada
runner@fv-az454-559:~$ chmod -R 640 /home/runner/karmada
runner@fv-az454-559:~$ mkdir /home/runner/karmada/pki
mkdir: cannot create directory ‘/home/runner/karmada/pki’: Permission denied

As you see, if you chmod 640 to one directory, the directory equal to readonly, the mod of directory should be at lease 700~

more example as follows:

runner@fv-az454-559:~$ mkdir /home/runner/karmada
runner@fv-az454-559:~$ chmod -R 700 /home/runner/karmada
runner@fv-az454-559:~$ mkdir /home/runner/karmada/pki
runner@fv-az454-559:~$ chmod -R 700 /home/runner/karmada/pki
runner@fv-az454-559:~$ touch /home/runner/karmada/pki/xx.txt 
runner@fv-az454-559:~$ ls /home/runner/karmada/pki/xx.txt
/home/runner/karmada/pki/xx.txt

runner@fv-az454-559:~$ mkdir /home/runner/karmada
runner@fv-az454-559:~$ chmod -R 700 /home/runner/karmada
runner@fv-az454-559:~$ mkdir /home/runner/karmada/pki
runner@fv-az454-559:~$ chmod -R 640 /home/runner/karmada/pki
runner@fv-az454-559:~$ touch /home/runner/karmada/pki/xx.txt 
touch: cannot touch '/home/runner/karmada/pki/xx.txt': Permission denied

700 is enough in our case, while, directory usually chmod to 750 in general.

[chaosi-zju]

I think you may not changed completed~

[zishen]

I think you may not changed completed~

yea, thanks a lot.

[vincentgoat]

lgtm

[RainbowMango]

/lgtm
/approve

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango, vincentgoat

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:

• operator/OWNERS [RainbowMango]
• pkg/karmadactl/cmdinit/OWNERS [RainbowMango]

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