Skip to content

feat(proposals): support image registry#1076

Open
jbrockopp wants to merge 2 commits intomainfrom
feat/proposal/image_registry
Open

feat(proposals): support image registry#1076
jbrockopp wants to merge 2 commits intomainfrom
feat/proposal/image_registry

Conversation

@jbrockopp
Copy link
Copy Markdown
Contributor

xref: #1066

This proposes adding support to Vela for providing warnings for specific container images whens used in a pipeline.

Additionally, in special scenarios, we'd like to explicitly block certain images from being used in a pipeline.

@jbrockopp jbrockopp self-assigned this Jan 20, 2026
@jbrockopp jbrockopp requested a review from a team as a code owner January 20, 2026 16:17
Copy link
Copy Markdown
Collaborator

@wass3r wass3r left a comment

Choose a reason for hiding this comment

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

looks good. thank you (also for the other random fixes).

out of the gate, i think it would be best if the list was database-backed and immediately enforceable (without a redeploy/restart), so ingesting a config file on startup seems not ideal.

looking forward to this.

@jbrockopp
Copy link
Copy Markdown
Contributor Author

@wass3r thanks for following up and sharing that feedback!

out of the gate, i think it would be best if the list was database-backed and immediately enforceable (without a redeploy/restart), so ingesting a config file on startup seems not ideal.

Sounds good! We had similar discussions on our end so we're aligned. However, before we move forward with implementation, is it safe to say there aren't any further discussions warranted for this functionality? We're happy to move forward with Option 2 from the proposal but want to ensure we've given enough time for others to share any feedback.

@KellyMerrick
Copy link
Copy Markdown
Contributor

I like it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants