Trident-operator incorrectly processes the imageRegistry parameter in the TridentOrchestrator resource
Applies to
Trident 25.02
Issue
- In Trident 25.02 the trident-operator incorrectly processes the imageRegistry parameter in the TridentOrchestrator resource.
- Event entries for the affected pod:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 5m34s default-scheduler Successfully assigned kube-system/trident-node-linux-ftwmt to pool3-bm08s1-eph
Normal Pulling 5m34s kubelet Pulling image "registry.eccd.local:5000/trident:25.02.0-7a8f590a"
Normal Pulled 5m33s kubelet Successfully pulled image "registry.eccd.local:5000/trident:25.02.0-7a8f590a" in 972ms (972ms including waiting). Image size: 77266169 bytes.
Normal Created 5m33s kubelet Created container: trident-main
Normal Started 5m33s kubelet Started container trident-main
Warning InspectFailed 4m37s (x9 over 5m33s) kubelet Failed to apply default image tag "registry.eccd.local:5000/": couldn't parse image name "registry.eccd.local:5000/": invalid reference format
Warning Failed 4m37s (x9 over 5m33s) kubelet Error: InvalidImageName
Warning Unhealthy 32s (x45 over 5m13s) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503
