-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
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
FIX | k3s-cis-*- CHECK 4.2.1-4.2.3 #1739
FIX | k3s-cis-*- CHECK 4.2.1-4.2.3 #1739
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aprilpear9696
It seems it makes sense!
thanks for the contribute!
@mozillazg wdyt? |
cc @andypitcher |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks for your contribution!
@mozillazg @afdesk Thanks for review. Could you help to reapprove to trigger the required validation before merge? Thanks |
merged |
The check 4.2.1-4.2.3 for k3s-cis-* is aim to check the node kubelet status. But current test case audit/audit_config commands are targeting kube-apiserver instead of kubelet.
Update the target tests' audit/audit_config command from checking kube-apiserver arguments to checking kubelet ones.