From ec3b1076c0a8cf20b0a2439f94c9739c8ea4e7c8 Mon Sep 17 00:00:00 2001
From: Roberto Rojas <robertojrojas@gmail.com>
Date: Fri, 30 Aug 2019 12:33:14 -0400
Subject: [PATCH] Fixes issue #407 (#409)
* fixes issue #407
* fixes issue #407
---
cfg/1.11-json/node.yaml | 8 ++++++++
cfg/1.13-json/node.yaml | 8 ++++++++
2 files changed, 16 insertions(+)
diff --git a/cfg/1.11-json/node.yaml b/cfg/1.11-json/node.yaml
index aace6e1..5ea7de2 100644
--- 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
diff --git a/cfg/1.13-json/node.yaml b/cfg/1.13-json/node.yaml
index 1f70296..394ebc8 100644
--- 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
--
GitLab