whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

trying to fix line breaks in raw blocks in list (#4997)

Browse Source 
Lets see on deploy preview if adding block type helps.
This commit is contained in:
Vladimir Rutsky
2017-08-17 22:42:13 +02:00
committed by Steve Perry
parent cf8b1bc6f7
commit fd1704e2c9
1 changed files with 32 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tutorials/clusters/apparmor.md
+4 -4
View File
@@ -44,7 +44,7 @@ Make sure:
will **silently ignore** any AppArmor settings that are provided. To ensure that your Pods are will **silently ignore** any AppArmor settings that are provided. To ensure that your Pods are
receiving the expected protections, it is important to verify the Kubelet version of your nodes: receiving the expected protections, it is important to verify the Kubelet version of your nodes:
``` ```shell
$ kubectl get nodes -o=jsonpath=$'{range .items[*]}{@.metadata.name}: {@.status.nodeInfo.kubeletVersion}\n{end}' $ kubectl get nodes -o=jsonpath=$'{range .items[*]}{@.metadata.name}: {@.status.nodeInfo.kubeletVersion}\n{end}'
gke-test-default-pool-239f5d02-gyn2: v1.4.0 gke-test-default-pool-239f5d02-gyn2: v1.4.0
gke-test-default-pool-239f5d02-x1kf: v1.4.0 gke-test-default-pool-239f5d02-x1kf: v1.4.0
@@ -56,7 +56,7 @@ Make sure:
default, such as Ubuntu and SUSE, and many others provide optional support. To check whether the default, such as Ubuntu and SUSE, and many others provide optional support. To check whether the
module is enabled, check the `/sys/module/apparmor/parameters/enabled` file: module is enabled, check the `/sys/module/apparmor/parameters/enabled` file:
``` ```shell
$ cat /sys/module/apparmor/parameters/enabled $ cat /sys/module/apparmor/parameters/enabled
Y Y
``` ```
@@ -72,7 +72,7 @@ Make sure:
also supports AppArmor is Docker. As more runtimes add AppArmor support, the options will be also supports AppArmor is Docker. As more runtimes add AppArmor support, the options will be
expanded. You can verify that your nodes are running docker with: expanded. You can verify that your nodes are running docker with:
``` ```shell
$ kubectl get nodes -o=jsonpath=$'{range .items[*]}{@.metadata.name}: {@.status.nodeInfo.containerRuntimeVersion}\n{end}' $ kubectl get nodes -o=jsonpath=$'{range .items[*]}{@.metadata.name}: {@.status.nodeInfo.containerRuntimeVersion}\n{end}'
gke-test-default-pool-239f5d02-gyn2: docker://1.11.2 gke-test-default-pool-239f5d02-gyn2: docker://1.11.2
gke-test-default-pool-239f5d02-x1kf: docker://1.11.2 gke-test-default-pool-239f5d02-x1kf: docker://1.11.2
@@ -87,7 +87,7 @@ Make sure:
kernel, the Kubelet (>= v1.4) will reject the Pod. You can view which profiles are loaded on a kernel, the Kubelet (>= v1.4) will reject the Pod. You can view which profiles are loaded on a
node by checking the `/sys/kernel/security/apparmor/profiles` file. For example: node by checking the `/sys/kernel/security/apparmor/profiles` file. For example:
``` ```shell
$ ssh gke-test-default-pool-239f5d02-gyn2 "sudo cat /sys/kernel/security/apparmor/profiles | sort" $ ssh gke-test-default-pool-239f5d02-gyn2 "sudo cat /sys/kernel/security/apparmor/profiles | sort"
apparmor-test-deny-write (enforce) apparmor-test-deny-write (enforce)
apparmor-test-audit-write (enforce) apparmor-test-audit-write (enforce)