-
Notifications
You must be signed in to change notification settings - Fork 350
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
Can't install Camel-K 2.0 nightly on OpenShift cluster #4476
Comments
bouskaJ
changed the title
Can't install Camel-K 2.0 nightly on OCP
Can't install Camel-K 2.0 nightly on OpenShift cluster
Jun 12, 2023
@squakez I will look into it. |
Ok, so the volumes can't be mounted in root mode by the operator pod when deploying in an OCP newly created project that is not |
gansheer
added a commit
to gansheer/camel-k
that referenced
this issue
Jun 14, 2023
…lity Ref apache#4476 * replase 1000 user by nonRoot option on builder pod * remove 0 (root) user for FS mounts on operator pod
gansheer
added a commit
to gansheer/camel-k
that referenced
this issue
Jun 23, 2023
Ref apache#4476 * replace 1001 user/group by a valid user compatible with SecurityContextConstraint user range from namespace label * remove 0 (root) user for FS mounts on operator pod
gansheer
added a commit
to gansheer/camel-k
that referenced
this issue
Jun 23, 2023
Ref apache#4476 * replace 1001 user/group by a valid user compatible with SecurityContextConstraint user range from namespace label * remove 0 (root) user for FS mounts on operator pod
gansheer
added a commit
to gansheer/camel-k
that referenced
this issue
Jun 23, 2023
Ref apache#4476 * replace 1001 user/group by a valid user compatible with SecurityContextConstraint user range from namespace label * remove 0 (root) user for FS mounts on operator pod
We should have closed this by #4487 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am getting following error
trying to install Camel-K operator on OpenShift.
The full scenario:
The text was updated successfully, but these errors were encountered: