You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After ComplianceAsCode/content#10464 all but one kubelet rule was being parsed to be under checkType: Node. However one rule (kubelet_configure_tls_min_version) wasn't updated to remove the warnings field.
This rule ends up being parsed/imported into k8s by CO as a checkType: Platform. While trying to tailor out/disable rules, this rule is impossible to tailor.
In this case, the kubelet_configure_tls_min_version rule would still run under the node scans, however CO would mark the TailoredProfile in ERROR when trying to disable this rule for a Node profile. If tailored out in a Platform profile, it has no effect on the Node scan.
The text was updated successfully, but these errors were encountered:
After ComplianceAsCode/content#10464 all but one kubelet rule was being parsed to be under
checkType: Node. However one rule (kubelet_configure_tls_min_version) wasn't updated to remove thewarningsfield.This rule ends up being parsed/imported into k8s by CO as a
checkType: Platform. While trying to tailor out/disable rules, this rule is impossible to tailor.Related PR to correct rule to be marked as Node type: ComplianceAsCode/content#11243
In this case, the
kubelet_configure_tls_min_versionrule would still run under the node scans, however CO would mark the TailoredProfile in ERROR when trying to disable this rule for a Node profile. If tailored out in a Platform profile, it has no effect on the Node scan.The text was updated successfully, but these errors were encountered: