[k3s][node][4.2.4][release/0.6] fix audit for --read-only-port discovery #569
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
swastik959
changed the title
andypitcher
requested changes
Nov 29, 2025
Contributor
andypitcher
left a comment
andypitcher
left a comment
There was a problem hiding this comment.
Wrong indentation, could you verify the other PRs as well ? Otherwise let's wait on #568 to get reviewed and merged to rebase your PRs.
…turned data The former audit returned too much data, which was subsequently truncated by kube-bench, causing the check to fail consistently. Signed-off-by: Andy Pitcher <[email protected]>
andypitcher
approved these changes
Dec 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description:
Check: 4.2.4 Verify that if defined, the --read-only-port argument is set to 0 (Automated)
The former audit returned too much data, which was subsequently truncated by kube-bench, causing the check to fail consistently. This fix improves the audit for --read-only-port discovery by limiting the returned data, piping the initial command to grep with -o, --only-matching.
Parent issue:
rancher/compliance-operator#123
Fixed versions:
Expected behaviour: By default, K3s sets the --read-only-port to 0 (which disables the read only kubelet API traditionally served on port 10255, preventing unauthenticated access to potentially sensitive cluster information).