From c594c0beee106889dabc423ec52b8600e58cd96e Mon Sep 17 00:00:00 2001 From: Marcin Owsiany Date: Tue, 23 Apr 2024 10:52:06 +0200 Subject: [PATCH] Use a real check in example AFAICT there is no `privileged` check ATM. --- docs/configuring-kubelinter.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-kubelinter.md b/docs/configuring-kubelinter.md index a0427c5b7..3411df6ee 100644 --- a/docs/configuring-kubelinter.md +++ b/docs/configuring-kubelinter.md @@ -103,12 +103,12 @@ example, To ignore violations for specific objects, users can add an annotation with the key `ignore-check.kube-linter.io/`. We strongly encourage adding an explanation as the value for the annotation. -For example, to ignore a check named "privileged" for a specific deployment, you can add an annotation like that: +For example, to ignore a check named "privileged-container" for a specific deployment, you can add an annotation like that: ```yaml metadata: annotations: - ignore-check.kube-linter.io/privileged: "This deployment needs to run as privileged because it needs kernel access" + ignore-check.kube-linter.io/privileged-container: "This deployment needs to run as privileged because it needs kernel access" ``` To ignore _all_ checks for a specific object, you can use the special annotation key `kube-linter.io/ignore-all`.