Fixes issue #407 (#409)

* fixes issue #407 * fixes issue #407
5 years ago · ec3b1076c0
parent 13dfa15ad6
commit ec3b1076c0
2 changed files with 16 additions and 0 deletions
--- a/cfg/1.11-json/node.yaml
+++ b/cfg/1.11-json/node.yaml
@ -436,6 +436,10 @@ groups:
        Run the below command (based on the file location on your system) on the each worker
        node. For example,
        chmod 644 $proxykubeconfig
+
+        Note - This test reports "FAIL" if kube-proxy has been configured
+        using a kubernetes configMap. Only under this situation, the "FAIL" can safely be ignored 
+        as the kube-proxy does not expose the kubeconfig file to the worker node.
      scored: true

    - id: 2.2.6
@ -449,6 +453,10 @@ groups:
          Run the below command (based on the file location on your system) on the each worker
          node. For example,
          chown root:root $proxykubeconfig
+                 
+          Note - This test reports "FAIL" if kube-proxy has been configured
+          using a kubernetes configMap. Only under this situation, the "FAIL" can safely be ignored 
+          as the kube-proxy does not expose the kubeconfig file to the worker node.
      scored: true

    - id: 2.2.7
--- a/cfg/1.13-json/node.yaml
+++ b/cfg/1.13-json/node.yaml
@ -417,6 +417,10 @@ groups:
        Run the below command (based on the file location on your system) on the each worker
        node. For example,
        chmod 644 $proxykubeconfig
+
+        Note - This test reports "FAIL" if kube-proxy has been configured
+        using a kubernetes configMap. Only under this situation, the "FAIL" can safely be ignored 
+        as the kube-proxy does not expose the kubeconfig file to the worker node.
      scored: true

    - id: 2.2.6
@ -430,6 +434,10 @@ groups:
          Run the below command (based on the file location on your system) on the each worker
          node. For example,
          chown root:root $proxykubeconfig
+          
+          Note - This test reports "FAIL" if kube-proxy has been configured
+          using a kubernetes configMap. Only under this situation, the "FAIL" can safely be ignored 
+          as the kube-proxy does not expose the kubeconfig file to the worker node.
      scored: true

    - id: 2.2.7