From eb7cfb731da7dd7ef6a2e7fdc88313f30ed432ef Mon Sep 17 00:00:00 2001 From: xeniape Date: Thu, 30 Jul 2026 08:36:32 +0200 Subject: [PATCH] chore: Fix kyverno link --- .../pages/enabling_verification_of_image_signatures.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/tutorials/pages/enabling_verification_of_image_signatures.adoc b/modules/tutorials/pages/enabling_verification_of_image_signatures.adoc index 695128865..5feff2058 100644 --- a/modules/tutorials/pages/enabling_verification_of_image_signatures.adoc +++ b/modules/tutorials/pages/enabling_verification_of_image_signatures.adoc @@ -31,5 +31,5 @@ kubectl apply -f kyverno-policy.yaml ---- The policy will be applied to all namespaces in the cluster. It checks all newly created Pods that run any image matching the expression `docker.stackable.tech/+++*+++` (all images provided by Stackable) and ensures that these images have been signed by a Stackable Github Action (`https://github.com/stackabletech/+++*+++/.github/workflows/build.yml@refs/+++*+++`). If the signature of an image is invalid or missing, the policy will deny the pod creation. -For a more detailed explanation of the policy options, please refer to the https://kyverno.io/docs/writing-policies/verify-images/sigstore/#keyless-signing-and-verification[Kyverno documentation]. +For a more detailed explanation of the policy options, please refer to the https://kyverno.io/docs/policy-types/cluster-policy/verify-images/sigstore/#keyless-signing-and-verification[Kyverno documentation]. If the `subject` field in the policy is changed to something like `https://github.com/test/+++*+++`, the policy will deny the creation of pods with Stackable images because the signature is no longer valid.