-
Story
-
Resolution: Not a Bug
-
Major
-
None
-
1.7.0.GA
-
False
-
False
-
Undefined
When using the new Connect build feature on OpenShift, we also have to link the registry.redhat.io secret to the default service account and this results in the following error when connect pod starts after a successful build:
9m2s Normal BackOff pod/my-connect-connect-8c4cd9db8-ppvct Back-off pulling image "image-registry.openshift-image-registry.svc@sha256:0446d984d18f1a8445face57dd9be538ba9bc2594e8f3a3fdf02486275be6b16" 32m Warning Failed pod/my-connect-connect-8c4cd9db8-ppvct Error: ErrImagePull 32m Warning Failed pod/my-connect-connect-8c4cd9db8-ppvct Failed to pull image "image-registry.openshift-image-registry.svc@sha256:0446d984d18f1a8445face57dd9be538ba9bc2594e8f3a3fdf02486275be6b16": rpc error: code = Unknown desc = Error reading manifest sha256:0446d984d18f1a8445face57dd9be538ba9bc2594e8f3a3fdf02486275be6b16 in docker.io/library/image-registry.openshift-image-registry.svc: errors: denied: requested access to the resource is denied unauthorized: authentication required
The way to fix this is to disable that secret in KafkaConnect CR:
spec:
# ...
template:
pod:
imagePullSecrets: []
We may need to document this somewhere.
