From 40c59ee37760b9bb28f0c56e3c4fc545a40661b0 Mon Sep 17 00:00:00 2001 From: John Krug Date: Thu, 28 Nov 2024 14:25:03 +0100 Subject: [PATCH] Chnages to test supporting a new approach t referencing lines inside a code block. Signed-off-by: John Krug --- docs/next/modules/en/pages/reference/monitor-mode.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/next/modules/en/pages/reference/monitor-mode.adoc b/docs/next/modules/en/pages/reference/monitor-mode.adoc index b3c1fad..399d82d 100644 --- a/docs/next/modules/en/pages/reference/monitor-mode.adoc +++ b/docs/next/modules/en/pages/reference/monitor-mode.adoc @@ -27,8 +27,9 @@ The `mode` is an attribute included in the `ClusterAdmissionPolicy` and `Admissi There are two values that the `mode` attribute can assume: `monitor` and `protect`. The `mode` defaults to `protect` if omitted. -To create a policy in `monitor mode` you to need include the `mode: monitor` as part of the specification of the resource. -For example, as highlighted, in this `ClusterAdmissionPolicy`: +To create a policy in `monitor mode` you to need to include the statement `mode: +monitor` as part of the specification of the resource. For example, in the +`spec` section (marked ➀), of this `ClusterAdmissionPolicy`: [subs="+attributes",yaml] ---- @@ -37,8 +38,7 @@ kind: ClusterAdmissionPolicy metadata: name: psp-capabilities spec: -// highlight-next-line - mode: monitor + mode: monitor <1> policyServer: reserved-instance-for-tenant-a module: registry://ghcr.io/kubewarden/policies/psp-capabilities:v0.1.3 rules: @@ -55,6 +55,7 @@ spec: required_drop_capabilities: - NET_ADMIN ---- +<1> The `mode: monitor` attribute is in the `spec` section. == Changing policy mode