From ee588f6d2badb3c0ccca204c848d85bd45497d57 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Sat, 16 Oct 2021 12:24:32 +0100 Subject: [PATCH] Write headings in sentence case Other than page titles, headings should be sentence case --- content/en/docs/tutorials/clusters/seccomp.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/docs/tutorials/clusters/seccomp.md b/content/en/docs/tutorials/clusters/seccomp.md index e3705f5d38..a160e08542 100644 --- a/content/en/docs/tutorials/clusters/seccomp.md +++ b/content/en/docs/tutorials/clusters/seccomp.md @@ -57,7 +57,7 @@ run as `Unconfined`. -## Create Seccomp Profiles +## Download example seccomp profiles {#download-profiles} The contents of these profiles will be explored later on, but for now go ahead and download them into a directory named `profiles/` so that they can be loaded @@ -91,7 +91,7 @@ audit.json fine-grained.json violation.json ``` -## Create a Local Kubernetes Cluster with kind +## Create a local Kubernetes cluster with kind For simplicity, [kind](https://kind.sigs.k8s.io/) can be used to create a single @@ -309,7 +309,7 @@ kubectl delete service audit-pod --wait kubectl delete pod audit-pod --wait --now ``` -## Create Pod with seccomp Profile that Causes Violation +## Create Pod with seccomp profile that causes violation For demonstration, apply a profile to the Pod that does not allow for any syscalls. @@ -349,7 +349,7 @@ kubectl delete service violation-pod --wait kubectl delete pod violation-pod --wait --now ``` -## Create Pod with seccomp Profile that Only Allows Necessary Syscalls +## Create Pod with seccomp profile that only allows necessary syscalls If you take a look at the `fine-pod.json`, you will notice some of the syscalls seen in the first example where the profile set `"defaultAction": @@ -428,7 +428,7 @@ kubectl delete service fine-pod --wait kubectl delete pod fine-pod --wait --now ``` -## Create Pod that uses the Container Runtime Default seccomp Profile +## Create Pod that uses the container runtime default seccomp profile Most container runtimes provide a sane set of default syscalls that are allowed or not. You can adopt these defaults for your workload by setting the seccomp