From bda7f1f5178c160e0dc2580e6e3a4f8e6c6611ff Mon Sep 17 00:00:00 2001 From: aimeeu Date: Tue, 1 Oct 2019 17:53:08 -0500 Subject: [PATCH] Modify apparmor.md based on PR - Fix site build (#16531) (#16648) Modify apparmor.md and delete .profile to enable the site to build with Hugo 0.57.2. Could not cherry pick PR 16531 because the Korean translation was added in 1.14. Signed-off-by: Aimee Ukasick --- content/en/docs/tutorials/clusters/apparmor.md | 13 ++++++++++++- .../en/docs/tutorials/clusters/deny-write.profile | 10 ---------- 2 files changed, 12 insertions(+), 11 deletions(-) delete mode 100644 content/en/docs/tutorials/clusters/deny-write.profile diff --git a/content/en/docs/tutorials/clusters/apparmor.md b/content/en/docs/tutorials/clusters/apparmor.md index 4e1fff809e..edbb55b320 100644 --- a/content/en/docs/tutorials/clusters/apparmor.md +++ b/content/en/docs/tutorials/clusters/apparmor.md @@ -178,7 +178,18 @@ k8s-apparmor-example-deny-write (enforce) First, we need to load the profile we want to use onto our nodes. The profile we'll use simply denies all file writes: -{{< code language="text" file="deny-write.profile" >}} +```shell +#include + +profile k8s-apparmor-example-deny-write flags=(attach_disconnected) { + #include + + file, + + # Deny all file writes. + deny /** w, +} +``` Since we don't know where the Pod will be scheduled, we'll need to load the profile on all our nodes. For this example we'll just use SSH to install the profiles, but other approaches are diff --git a/content/en/docs/tutorials/clusters/deny-write.profile b/content/en/docs/tutorials/clusters/deny-write.profile deleted file mode 100644 index c2653c7112..0000000000 --- a/content/en/docs/tutorials/clusters/deny-write.profile +++ /dev/null @@ -1,10 +0,0 @@ -#include - -profile k8s-apparmor-example-deny-write flags=(attach_disconnected) { - #include - - file, - - # Deny all file writes. - deny /** w, -}