Job for LTPA generation could use outdated configuration

[leochr]

The following configurations from the WebSphereLibertyApplication CR instance (leader) are set on the LTPA Job when created. However, once the Job is created, these configurations could be outdated/out-of-sync if the user changes the value in the CR. This is not an issue if the Job completed successfully with the initial configuration. But otherwise it could be stuck due to invalid configuration - although the user had updated the CR with the correct configuration later on (i.e. invalid image pull secret is initially specified, Job is created with it, user updates the secret value afterwards):

• image pull secret
• image pull policy
• security context

---

• Delivered to WLO
• Delivered to OLO
• Tests

[leochr]

@kabicin WLO PR looks good. Merged it. Please create OLO PR when you get a chance. Thank you