improve security with CIS Kubernetes V1.23 Benchmark item number 4.1.9

[satandyh]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Improve security with CIS Kubernetes V1.23 Benchmark item number 4.1.9
Ref to https://github.com/aquasecurity/kube-bench/blob/main/cfg/cis-1.23/node.yaml#L131

Also because there present additional config file kubelet.env. It's permissions also changed to the same as for kubelet-config.yaml.

Which issue(s) this PR fixes:

Fixes #10302

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Fix CIS Kubernetes V1.23 Benchmark item number 4.1.9 to enhance security (Change kubelet-config.yaml and kubelet.env file permissions from 640 to 600)

[linux-foundation-easycla]

• ❌ The email address for the commit (c634c05) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Welcome @satandyh!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @satandyh. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[MrFreezeex]

Hi could you check what's up with the cla? It appear that the email address you are using to commit is not on your GitHub profile.

[yankay]

/ok-to-test

[satandyh]

Hi could you check what's up with the cla? It appear that the email address you are using to commit is not on your GitHub profile.

Hello, @MrFreezeex
yep I missed it to add to GitHub, my fault. Because I often use more than one laptop with different configurations. I have added my email from the PR to my GitHub account. Check the proof in the link below (it's png image on google drive). Let me know if I need to perform any additional steps.

https://drive.google.com/file/d/1LaAdS8EhXj8h0yixXpkAZwigMthWEiGS/view?usp=sharing

[MrFreezeex]

Thanks! It's not really that I need a proof or anything but the CI will not be able to merge your PR if it has not the label. Anyway thanks for fixing it :D.
/lgtm
/ok-to-test

[yankay]

@satandyh Thanks

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MrFreezeex, satandyh, yankay

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:

• OWNERS [yankay]

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