The variables for the  kubelet config rules are not working as expected    

4.17.0-0.nightly-2024-08-07-124849 + compliance-operator.v1.5.0    

Always    

1. Install Compliance Operator 
2. Create a tp with below yaml file:
apiVersion: compliance.openshift.io/v1alpha1
kind: TailoredProfile
metadata:
  name: testprofile
  namespace: openshift-compliance
  annotations:
    compliance.openshift.io/product-type: Node
spec:
  description: test
  title: test-node
  enableRules:
    - name: ocp4-kubelet-enable-server-cert-rotation
      rationale: test
    - name: ocp4-kubelet-enable-streaming-connections
      rationale: test
    - name: ocp4-kubelet-eviction-thresholds-set-hard-imagefs-available
      rationale: test
    - name: ocp4-kubelet-eviction-thresholds-set-hard-imagefs-inodesfree
      rationale: test
    - name: ocp4-kubelet-eviction-thresholds-set-hard-memory-available
      rationale: test
    - name: ocp4-kubelet-eviction-thresholds-set-hard-nodefs-available
      rationale: test
    - name: ocp4-kubelet-eviction-thresholds-set-hard-nodefs-inodesfree
      rationale: test
  setValues:
    - name: ocp4-var-kubelet-evictionhard-imagefs-available
      value: "20%"
      rationale: test
    - name: ocp4-var-kubelet-evictionhard-imagefs-inodesfree
      value: "8%"
      rationale: test
    - name: ocp4-var-kubelet-evictionhard-memory-available
      value: "400Mi"
      rationale: test
    - name: ocp4-var-kubelet-evictionhard-nodefs-available
      value: "12%"
      rationale: test
    - name: ocp4-var-kubelet-evictionhard-nodefs-inodesfree
      value: "6%"
      rationale: test
    - name: ocp4-var-streaming-connection-timeouts
      value: "5h0m0s"
      rationale: test

3. Create a ssb with below yaml file:
% cat ssb_tp.yaml 
apiVersion: compliance.openshift.io/v1alpha1
kind: ScanSettingBinding
metadata:
  name: test
profiles:
  - apiGroup: compliance.openshift.io/v1alpha1
    kind: TailoredProfile
    name: testprofile
settingsRef:
  apiGroup: compliance.openshift.io/v1alpha1
  kind: ScanSetting
  name: default
4. Check the scan result

The compliance suite returns COMPLIANT
% oc get suite
NAME   PHASE   RESULT
test   DONE    COMPLIANT    

The variables should take effect and return the scan result that reflects the actual status.