-
Notifications
You must be signed in to change notification settings - Fork 15
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
Pods can't be started on OCP 3.x clusters with default configuration #41
Comments
The reason of this BUG is that OCP 3.11 has a default SCC that prevents userID with low numbers, such as 200 (the one Nexus uses). To fix this, a custom SCC must be created in the namespace. See: https://docs.openshift.com/container-platform/3.11/install_config/persistent_storage/pod_security_context.html We will document and add a SCC example to the project to help administrators have the operator working on OCP 3.11 clusters. |
Pushing to 0.2.0, if we have the time by the end of the milestone we should include this one. |
Make Deployments use the ServiceAccount informed in `nexus.spec.serviceAccountName`. If none is informed the default SA created by the operator-sdk in `deploy/`is used. Assumes the default account has not been deleted, the Deployment will trigger an event otherwise. Fix m88i#41 by adding SCCs which can be used by the cluster admin and documenting their use. Signed-off-by: Lucas Caparelli <lucas.caparelli112@gmail.com>
Make Deployments use the ServiceAccount informed in `nexus.spec.serviceAccountName`. If none is informed the default SA created by the operator-sdk in `deploy/`is used. Assumes the default account has not been deleted, the Deployment will trigger an event otherwise. Fix m88i#41 by adding SCCs which can be used by the cluster admin and documenting their use. Signed-off-by: Lucas Caparelli <lucas.caparelli112@gmail.com>
Create default RBAC resources for use by the Operator. Make Deployments use the ServiceAccount informed in `nexus.spec.serviceAccountName`. If none is informed the default SA created by the Operator is used. Fix m88i#41 by adding SCCs which can be used by the cluster admin and documenting their use. Signed-off-by: Lucas Caparelli <lucas.caparelli112@gmail.com>
Create default RBAC resources for use by the Operator. Make Deployments use the ServiceAccount informed in `nexus.spec.serviceAccountName`. If none is informed the default SA created by the Operator is used. Fix m88i#41 by adding SCCs which can be used by the cluster admin and documenting their use. Signed-off-by: Lucas Caparelli <lucas.caparelli112@gmail.com>
Create default RBAC resources for use by the Operator. Make Deployments use the ServiceAccount informed in `nexus.spec.serviceAccountName`. If none is informed the default SA created by the Operator is used. Fix m88i#41 by adding SCCs which can be used by the cluster admin and documenting their use. Signed-off-by: Lucas Caparelli <lucas.caparelli112@gmail.com>
Create default RBAC resources for use by the Operator. Make Deployments use the ServiceAccount informed in `nexus.spec.serviceAccountName`. If none is informed the default SA created by the Operator is used. Fix m88i#41 by adding SCCs which can be used by the cluster admin and documenting their use. Signed-off-by: Lucas Caparelli <lucas.caparelli112@gmail.com>
When attempting to deploy to an OCP 3.x cluster the following error pops up:
As Nexus must run using this UID the cluster administrator needs to create a scc to work around this. It would be nice if we could supply this scc and have this documented.
The text was updated successfully, but these errors were encountered: