Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: clarify that variables are not allowed in imageReferences field #1472

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+63 −0
Open

docs: clarify that variables are not allowed in imageReferences field #1472

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3d1db6d
docs: clarify that variables are not allowed in imageReferences field
kushal9897 Feb 8, 2025
ad2320c
docs(index.md): clarify variable restrictions in imageReferences
kushal9897 Feb 11, 2025
fefddd8
docs: clarify that preconditions are not allowed in imageReferences f…
kushal9897 Feb 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions content/en/docs/writing-policies/verify-images/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,17 @@ The `imageRegistryCredentials.secrets` specifies a list of secrets that are prov

For additional details please reference a section below for the solution used to sign the images and attestations:

## Limitations

### Variables in `imageReferences`
The `imageReferences` field does **not** support variable interpolation (e.g., `{{ }}` syntax). Only **static strings** or predefined lists should be used.

#### **Incorrect Usage**
```yaml
verifyImages:
- imageReferences: ["{{ parse_yaml(allowedregistryprefixes.data.allowedregistryprefixes) }}"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate example.



### Cache

Image verification requires multiple network calls and can be time consuming. Kyverno has a TTL based cache for image verification which caches successful outcomes of image verification. When cache is enabled, an image once verified by a policy will be considered to be verified until TTL duration expires or there is a change in policy.
Expand Down
Loading