I am seeing the following errors for the WLO application. While talking to @kabicin, this is happening as the operator is trying to verify that Liberty image supports this new feature of custom AES keys. I have global pull-secret defined and which is used correctly to pull application images. WLO is also installed at cluster level. So WLO/OLO should be able to use global pull-secret. Looks like, I am missing Liberty version verification.
conditions:
- lastTransitionTime: '2026-03-18T19:05:17Z'
message: Resources are not ready.
reason: ResourcesNotReady
status: 'False'
type: Ready
- lastTransitionTime: '2026-03-18T17:58:15Z'
status: 'True'
type: Reconciled
- lastTransitionTime: '2026-03-18T19:05:17Z'
message: 'StatefulSet replicas ready: 0 < minReplicas: 1'
reason: MinimumReplicasUnavailable
status: 'False'
type: ResourcesReady
- lastTransitionTime: '2026-03-18T19:05:17Z'
message: Failed to pull container image metadata; unauthorized or the image does not exist
status: 'True'
type: Warning
I am seeing the following errors for the WLO application. While talking to @kabicin, this is happening as the operator is trying to verify that Liberty image supports this new feature of custom AES keys. I have global pull-secret defined and which is used correctly to pull application images. WLO is also installed at cluster level. So WLO/OLO should be able to use global pull-secret. Looks like, I am missing Liberty version verification.