-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in OpenShift image-pull delegation on IBM Cloud #2530
Comments
Workaround is to manually create the following rolebinding:
Replacing |
nicolaferraro
added a commit
that referenced
this issue
Jul 28, 2021
nicolaferraro
added a commit
that referenced
this issue
Jul 29, 2021
nicolaferraro
added a commit
that referenced
this issue
Jul 29, 2021
astefanutti
pushed a commit
that referenced
this issue
Jul 30, 2021
astefanutti
pushed a commit
that referenced
this issue
Jul 30, 2021
astefanutti
pushed a commit
to jboss-fuse/camel-k
that referenced
this issue
Aug 2, 2021
astefanutti
pushed a commit
to jboss-fuse/camel-k
that referenced
this issue
Aug 2, 2021
astefanutti
pushed a commit
to jboss-fuse/camel-k
that referenced
this issue
Aug 2, 2021
astefanutti
pushed a commit
that referenced
this issue
Aug 4, 2021
astefanutti
pushed a commit
that referenced
this issue
Aug 4, 2021
astefanutti
pushed a commit
that referenced
this issue
Aug 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The operator fails to create the RoleBinding that binds the
system:image-puller
ClusterRole
to the integration service account (pull-secret trait).This happens when the operator is installed globally and no
IntegrationPlatform
is created in the user namespace.The final result is that the pod can't start (image pull error).
Operator logs:
The text was updated successfully, but these errors were encountered: