From 7131711bb42fcb31d0621268f75683627a4939a5 Mon Sep 17 00:00:00 2001 From: Jim Bugwadia Date: Tue, 12 Nov 2019 17:34:21 -0800 Subject: [PATCH] fix typos --- samples/best_practices/disallow_bind_mounts.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/samples/best_practices/disallow_bind_mounts.yaml b/samples/best_practices/disallow_bind_mounts.yaml index f7d75dd835..c00b0bf190 100644 --- a/samples/best_practices/disallow_bind_mounts.yaml +++ b/samples/best_practices/disallow_bind_mounts.yaml @@ -6,10 +6,10 @@ metadata: policies.kyverno.io/category: Workload Isolation policies.kyverno.io/description: The volume of type `hostPath` allows pods to use host bind mounts (i.e. directories and volumes mounted to a host path) in containers. Using host - resources can be used to access shared data or escalate priviliges. Also, this couples pods + resources can be used to access shared data or escalate privileges. Also, this couples pods to a specific host and data persisted in the `hostPath` volume is coupled to the life of the - node leading to potential pod scheduling failures. It is highly recommeded that applications - are designed to be decoupled from the underlying infrstructure (in this case, nodes). + node leading to potential pod scheduling failures. It is highly recommended that applications + are designed to be decoupled from the underlying infrastructure (in this case, nodes). spec: rules: @@ -23,4 +23,4 @@ spec: pattern: spec: volumes: - - X(hostPath): null \ No newline at end of file + - X(hostPath): null