From 035fb4eff7488b7b91890b076d9e13bd5a1bd8f9 Mon Sep 17 00:00:00 2001 From: Min Khant Zaw <106727194+minkzaw@users.noreply.github.com> Date: Sat, 27 Jul 2024 19:24:03 +0630 Subject: [PATCH] Fixed typo for the 'keys' ConfigMap name (#1085) * Fixed typo for the 'keys' ConfigMap name Signed-off-by: Min Khant Zaw <106727194+minkzaw@users.noreply.github.com> Signed-off-by: minkzaw * Update artifact hub readme and hash Signed-off-by: minkzaw --------- Signed-off-by: Min Khant Zaw <106727194+minkzaw@users.noreply.github.com> Signed-off-by: minkzaw --- other/verify-image-with-multi-keys/artifacthub-pkg.yml | 4 ++-- .../verify-image-with-multi-keys.yaml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/other/verify-image-with-multi-keys/artifacthub-pkg.yml b/other/verify-image-with-multi-keys/artifacthub-pkg.yml index 886ef0e86..630316e2e 100644 --- a/other/verify-image-with-multi-keys/artifacthub-pkg.yml +++ b/other/verify-image-with-multi-keys/artifacthub-pkg.yml @@ -12,11 +12,11 @@ keywords: - kyverno - Software Supply Chain Security readme: | - There may be multiple keys used to sign images based on the parties involved in the creation process. This image verification policy requires the named image be signed by two separate keys. It will search for a global "production" key in a ConfigMap called `key` in the `default` Namespace and also a Namespace key in the same ConfigMap. + There may be multiple keys used to sign images based on the parties involved in the creation process. This image verification policy requires the named image be signed by two separate keys. It will search for a global "production" key in a ConfigMap called `keys` in the `default` Namespace and also a Namespace key in the same ConfigMap. Refer to the documentation for more details on Kyverno annotations: https://artifacthub.io/docs/topics/annotations/kyverno/ annotations: kyverno/category: "Software Supply Chain Security" kyverno/kubernetesVersion: "1.23" kyverno/subject: "Pod" -digest: 14cc8946fcc7d3141270826f036b28226c88c5d8e93ba475b1523e90512a281b +digest: 512b32c2d9e2bcf48907258ca01ff675efb4ed0d1967351ad161e50b20512d56 diff --git a/other/verify-image-with-multi-keys/verify-image-with-multi-keys.yaml b/other/verify-image-with-multi-keys/verify-image-with-multi-keys.yaml index 2c1592bde..4c77e2ce9 100644 --- a/other/verify-image-with-multi-keys/verify-image-with-multi-keys.yaml +++ b/other/verify-image-with-multi-keys/verify-image-with-multi-keys.yaml @@ -15,7 +15,7 @@ metadata: the parties involved in the creation process. This image verification policy requires the named image be signed by two separate keys. It will search for a global "production" - key in a ConfigMap called `key` in the `default` Namespace + key in a ConfigMap called `keys` in the `default` Namespace and also a Namespace key in the same ConfigMap. spec: validationFailureAction: enforce @@ -42,4 +42,4 @@ spec: - keys: publicKeys: "{{ keys.data.production }}" - keys: - publicKeys: "{{ keys.data.{{request.namespace}} }}" \ No newline at end of file + publicKeys: "{{ keys.data.{{request.namespace}} }}"