Remove extra period and the

Signed-off-by: Derek Nola <[email protected]>

package/cfg/k3s-cis-1.24-hardened/master.yaml

@@ -347,7 +347,7 @@ groups:
           Follow the documentation and configure alternate mechanisms for authentication.
           If this check fails, edit the K3s config file /etc/rancher/k3s/config.yaml and remove anything similar to below.
           kube-apiserver-arg:
-          - "token-auth-file=<path>".
+          - "token-auth-file=<path>"
         scored: true
 
       - id: 1.2.3
@@ -399,7 +399,7 @@ groups:
           By default, K3s automatically provides the kubelet client certificate and key.
           They are generated and located at /var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt and /var/lib/rancher/k3s/server/tls/client-kube-apiserver.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kube-apiserver-arg:
           - "kubelet-client-certificate=<path/to/client-cert-file>"
           - "kubelet-client-key=<path/to/client-key-file>"

package/cfg/k3s-cis-1.24-hardened/node.yaml

@@ -352,7 +352,7 @@ groups:
           By default, K3s automatically provides the TLS certificate and private key for the Kubelet.
           They are generated and located at /var/lib/rancher/k3s/agent/serving-kubelet.crt and /var/lib/rancher/k3s/agent/serving-kubelet.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kubelet-arg:
           - "tls-cert-file=<path/to/tls-cert-file>"
           - "tls-private-key-file=<path/to/tls-private-key-file>"

package/cfg/k3s-cis-1.24-permissive/master.yaml

@@ -347,7 +347,7 @@ groups:
           Follow the documentation and configure alternate mechanisms for authentication.
           If this check fails, edit the K3s config file /etc/rancher/k3s/config.yaml and remove anything similar to below.
           kube-apiserver-arg:
-          - "token-auth-file=<path>".
+          - "token-auth-file=<path>"
         scored: true
 
       - id: 1.2.3
@@ -400,7 +400,7 @@ groups:
           By default, K3s automatically provides the kubelet client certificate and key.
           They are generated and located at /var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt and /var/lib/rancher/k3s/server/tls/client-kube-apiserver.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kube-apiserver-arg:
           - "kubelet-client-certificate=<path/to/client-cert-file>"
           - "kubelet-client-key=<path/to/client-key-file>"

package/cfg/k3s-cis-1.24-permissive/node.yaml

@@ -357,7 +357,7 @@ groups:
           By default, K3s automatically provides the TLS certificate and private key for the Kubelet.
           They are generated and located at /var/lib/rancher/k3s/agent/serving-kubelet.crt and /var/lib/rancher/k3s/agent/serving-kubelet.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kubelet-arg:
           - "tls-cert-file=<path/to/tls-cert-file>"
           - "tls-private-key-file=<path/to/tls-private-key-file>"

package/cfg/k3s-cis-1.7-hardened/master.yaml

@@ -348,7 +348,7 @@ groups:
           Follow the documentation and configure alternate mechanisms for authentication.
           If this check fails, edit the K3s config file /etc/rancher/k3s/config.yaml and remove anything similar to below.
           kube-apiserver-arg:
-          - "token-auth-file=<path>".
+          - "token-auth-file=<path>"
         scored: true
 
       - id: 1.2.3
@@ -383,7 +383,7 @@ groups:
           By default, K3s automatically provides the kubelet client certificate and key.
           They are generated and located at /var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt and /var/lib/rancher/k3s/server/tls/client-kube-apiserver.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kube-apiserver-arg:
           - "kubelet-client-certificate=<path/to/client-cert-file>"
           - "kubelet-client-key=<path/to/client-key-file>"

package/cfg/k3s-cis-1.7-permissive/master.yaml

@@ -349,7 +349,7 @@ groups:
           Follow the documentation and configure alternate mechanisms for authentication.
           If this check fails, edit the K3s config file /etc/rancher/k3s/config.yaml and remove anything similar to below.
           kube-apiserver-arg:
-          - "token-auth-file=<path>".
+          - "token-auth-file=<path>"
         scored: true
 
       - id: 1.2.3
@@ -384,7 +384,7 @@ groups:
           By default, K3s automatically provides the kubelet client certificate and key.
           They are generated and located at /var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt and /var/lib/rancher/k3s/server/tls/client-kube-apiserver.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kube-apiserver-arg:
           - "kubelet-client-certificate=<path/to/client-cert-file>"
           - "kubelet-client-key=<path/to/client-key-file>"

package/cfg/k3s-cis-1.7-permissive/node.yaml

@@ -337,7 +337,7 @@ groups:
           By default, K3s automatically provides the TLS certificate and private key for the Kubelet.
           They are generated and located at /var/lib/rancher/k3s/agent/serving-kubelet.crt and /var/lib/rancher/k3s/agent/serving-kubelet.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kubelet-arg:
           - "tls-cert-file=<path/to/tls-cert-file>"
           - "tls-private-key-file=<path/to/tls-private-key-file>"

package/cfg/k3s-cis-1.8-hardened/master.yaml

@@ -348,7 +348,7 @@ groups:
           Follow the documentation and configure alternate mechanisms for authentication.
           If this check fails, edit the K3s config file /etc/rancher/k3s/config.yaml and remove anything similar to below.
           kube-apiserver-arg:
-          - "token-auth-file=<path>".
+          - "token-auth-file=<path>"
         scored: true
 
       - id: 1.2.3
@@ -383,7 +383,7 @@ groups:
           By default, K3s automatically provides the kubelet client certificate and key.
           They are generated and located at /var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt and /var/lib/rancher/k3s/server/tls/client-kube-apiserver.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kube-apiserver-arg:
           - "kubelet-client-certificate=<path/to/client-cert-file>"
           - "kubelet-client-key=<path/to/client-key-file>"

package/cfg/k3s-cis-1.8-hardened/node.yaml

@@ -330,7 +330,7 @@ groups:
           By default, K3s automatically provides the TLS certificate and private key for the Kubelet.
           They are generated and located at /var/lib/rancher/k3s/agent/serving-kubelet.crt and /var/lib/rancher/k3s/agent/serving-kubelet.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kubelet-arg:
           - "tls-cert-file=<path/to/tls-cert-file>"
           - "tls-private-key-file=<path/to/tls-private-key-file>"

package/cfg/k3s-cis-1.8-permissive/master.yaml

@@ -349,7 +349,7 @@ groups:
           Follow the documentation and configure alternate mechanisms for authentication.
           If this check fails, edit the K3s config file /etc/rancher/k3s/config.yaml and remove anything similar to below.
           kube-apiserver-arg:
-          - "token-auth-file=<path>".
+          - "token-auth-file=<path>"
         scored: true
 
       - id: 1.2.3
@@ -384,7 +384,7 @@ groups:
           By default, K3s automatically provides the kubelet client certificate and key.
           They are generated and located at /var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt and /var/lib/rancher/k3s/server/tls/client-kube-apiserver.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kube-apiserver-arg:
           - "kubelet-client-certificate=<path/to/client-cert-file>"
           - "kubelet-client-key=<path/to/client-key-file>"

package/cfg/k3s-cis-1.8-permissive/node.yaml

@@ -335,7 +335,7 @@ groups:
           By default, K3s automatically provides the TLS certificate and private key for the Kubelet.
           They are generated and located at /var/lib/rancher/k3s/agent/serving-kubelet.crt and /var/lib/rancher/k3s/agent/serving-kubelet.key
           If for some reason you need to provide your own certificate and key, you can set the
-          the below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
+          below parameters in the K3s config file /etc/rancher/k3s/config.yaml.
           kubelet-arg:
           - "tls-cert-file=<path/to/tls-cert-file>"
           - "tls-private-key-file=<path/to/tls-private-key-file>"