Make operator resilient to registry failure

With the upcoming Gitlab OTG coming, considerations towards how we handle image pulling were discussed between me and @jhensche .

This MR comes as a proposal of improvement to avoid application downtime due to container registry unavailability, by using a default pulling that will take advantage of the node cached image, and only resort to pull the image when not available in the node.

Part of cern-drupal-distribution#19 (closed) Part of https://gitlab.cern.ch/drupal/overview/-/issues/10

requested review from @crdeoliv and @ravineet

added 1 commit

• 030aa60b - Make new field overwrite the old one

Compare with previous version

added 6 commits

• 030aa60b...04d30b68 - 5 commits from branch master
• ccdf4985 - Make new field overwrite the old one

Compare with previous version

added 1 commit

• 5e19138c - Applied suggestions of refactoring and others

Compare with previous version

resolved all threads

changed the description

requested review from @vasvi and @jlopesda and removed review request for @ravineet

added 34 commits

• 5e19138c...58d0b3f0 - 32 commits from branch master
• dc5525fa - Make new field overwrite the old one
• 6035bc59 - Applied suggestions of refactoring and others

Compare with previous version

added 1 commit

• 36d2b65f - Tests later, they are currently failing

Compare with previous version

Comments for improvement: We do not enforce any policy for nginx and php-fpm due to the fact S2I will not work with image pull policy IfNotPresent.

Add condition to enforce depending on which case.

Comments for improvement: We do not enforce any policy for nginx and php-fpm due to the fact S2I will not work with image pull policy IfNotPresent.

Can you elaborate on this?

merged

mentioned in commit bc06b3ef