fix(security): add imagePullPolicy to operator deployment #7250
Conversation
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
We should always have an imagePullPolicy to make sure the operator images is always pulled avoiding using possible local and dangerous images. Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
|
❗ By default, the pull request is configured to backport to all release branches.
|
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
4 similar comments
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
gbartolini
approved these changes
Mar 28, 2025
mnencia
approved these changes
Apr 9, 2025
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
cnpg-bot
pushed a commit
that referenced
this pull request
Apr 9, 2025
We should always have an imagePullPolicy to make sure the operator images is always pulled avoiding using possible local and dangerous images. Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com> (cherry picked from commit a4c7dee)
cnpg-bot
pushed a commit
that referenced
this pull request
Apr 9, 2025
We should always have an imagePullPolicy to make sure the operator images is always pulled avoiding using possible local and dangerous images. Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com> (cherry picked from commit a4c7dee)
cnpg-bot
pushed a commit
that referenced
this pull request
Apr 9, 2025
We should always have an imagePullPolicy to make sure the operator images is always pulled avoiding using possible local and dangerous images. Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com> (cherry picked from commit a4c7dee)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We should always have an imagePullPolicy to make sure the operator
images is always pulled avoiding using possible local and dangerous images.