Conversation
wass3r
left a comment
There was a problem hiding this comment.
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.
|
@wass3r thanks for following up and sharing that feedback!
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. |
|
I like it! |
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.