blog: add blog for imagevalidating-policy#2040
Open
kirti763 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Kirti Goyal <kg4180553@gmail.com>
onasser1
reviewed
May 28, 2026
|
|
||
| **ImageValidatingPolicy** deals with something completely different. | ||
|
|
||
| Not configuration. **Trust**. |
Contributor
There was a problem hiding this comment.
Suggested change
| Not configuration. **Trust**. | |
| Not configuration. but **Trust**. |
onasser1
reviewed
May 28, 2026
Comment on lines
+20
to
+23
| When a Pod is scheduled and Kubernetes pulls a container image like how does the cluster | ||
| know that image is actually what it claims to be? How does it know the image wasn't | ||
| tampered with after it was built? How does it know it came from the CI pipeline and | ||
| not from somewhere else entirely? |
Contributor
There was a problem hiding this comment.
suggestion
Suggested change
| When a Pod is scheduled and Kubernetes pulls a container image like how does the cluster | |
| know that image is actually what it claims to be? How does it know the image wasn't | |
| tampered with after it was built? How does it know it came from the CI pipeline and | |
| not from somewhere else entirely? | |
| When a Pod is scheduled and Kubernetes pulls a container image, how does the cluster | |
| verify that image is actually what it claims to be? How does it ensure the image wasn't | |
| tampered with after it was built? How does it know it came from the CI pipeline and | |
| not from somewhere else entirely? |
onasser1
reviewed
May 28, 2026
Comment on lines
+12
to
+14
| The other policy covered so far deals with Kubernetes resource configuration. | ||
| Labels, resource limits, namespaces, cleanup schedules. All of it is about how | ||
| resources are configured. |
Contributor
There was a problem hiding this comment.
suggestion
@kirti763 if this intended to mention vpol, mpol, gpol etc. I think using plural policies might be better?
Suggested change
| The other policy covered so far deals with Kubernetes resource configuration. | |
| Labels, resource limits, namespaces, cleanup schedules. All of it is about how | |
| resources are configured. | |
| The other policies covered so far deal with Kubernetes resource configuration. Labels, resource limits, namespaces, and cleanup schedules are all about how resources are configured. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issue
Proposed Changes
Checklist