From e1ba9a975e36e660a58dea62f22a6fb347549540 Mon Sep 17 00:00:00 2001
From: Jean-Philippe Evrard <open-source@a.spamming.party>
Date: Thu, 29 Oct 2020 09:56:32 +0100
Subject: [PATCH] Remove kubectl exception in container scanning

Because we now have a builtin kubectl, we don't need that
security exception.
---
 .github/containerscan/allowedlist.yaml | 7 -------
 1 file changed, 7 deletions(-)
 delete mode 100644 .github/containerscan/allowedlist.yaml

diff --git a/.github/containerscan/allowedlist.yaml b/.github/containerscan/allowedlist.yaml
deleted file mode 100644
index 843f197..0000000
--- a/.github/containerscan/allowedlist.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-general:
-  bestPracticeViolations:
-    # We violate this rule because we add kubectl from a remote location
-    # Instead of building it from source/copying it.
-    # Until we change our practices (e.g. have Dockerfile build kubectl
-    # in a multi-staged manner), we should skip this check
-    - CIS-DI-0009