FusionAuth
image name fusionauth/fusionauth-app:1.60.2 returns ambiguous list on CRI-O 1.34.x
Describe the bug Running Helm chart version 1.60.2 after an upgrade to kubernetes 1.34.1 (Oracle OKE with CRI-O 1.34.1)
Pod doesn't start with a PodInspectError
and this event
- Warning InspectFailed 3m32s (x893 over 3h18m) kubelet Failed to inspect image "": rpc error: code = Unknown desc = short name mode is enforcing, but image name fusionauth/fusionauth-app:1.60.2 returns ambiguous list
This seems linked to https://github.com/cri-o/cri-o/pull/9401
See the Uncategorized section of the changelog for 1.34.0 https://github.com/cri-o/cri-o/releases:
Enable shortname enforcement, requiring shortnames to be unambiguous if there are multiple entries that could be pulled from the list of 'unqualified-search-registries'. Generally, users should not enable 'unqualified-search-registries' but if they must be used, they should be unambiguous (https://github.com/cri-o/cri-o/pull/9401, @haircommander)
I currently fixed the problem by modifying the value registry: from fusionauth/fusionauth-app:1.60.2 to docker.io/fusionauth/fusionauth-app:1.60.2
Docker version and underlying OS Kubernetes (OKE)1.34.1 CRI-O 1.34.1
To Reproduce Steps to reproduce the behavior:
- Deploy 1.60.2 on a 1.34.x cluster running CRI-O 1.34.0
Expected behavior Pod should start even on Kubernetes + CRI-O 1.34.0
