openshift.org | Source files used to build the https : //www.openshift.org

The use case trying out is, way to initialize the postgres database after it starts up. I saw the post start hooks in the openshift pod lifecycle. I can't put the sql statements using here-document or in command line ( Docker command fails due to max length issue ).

So looking a option to save the SQL statements in a file via ConfigMap and attach it to the post container before it starts, so that the psql command can execute it. I couldn't see a way to attach the volume from the DeploymentConfig from the official document. Is there any way I can do it ?

Document I referred - openshift-doc

It downloads openshift into C:\Users\[user]\.minishift\machines folder. How to change this location to, say, D:\My VMs\? The config set is not very helpful in explaining setting which config for which.

• Minishift verision: v1.15.1
• Platform: Windows
• Driver: Hyper-V

Any help would be greatly appreciated.

Trying to do an openshift 3.11 install with 3 master setup ,2 infra and 2 nodes. I didn't use a LB node since I figured the AWS ELB would take care of that for me.

My current issue is the installation will fail on the wait for control pane task.

From this reading on https://docs.openshift.org/latest/creating_images/guidelines.html#openshift-specific-guidelines in the section Support Arbitrary User IDs. It's recommended for:

• an image to support running an arbitrary user
• an image to make directories and files own by root group
• an image to declare USER with the user id, not the username

Example:

I am trying to run simple elk container with openshift(using minishift). The image I am trying to run is this elk image. During image deploy to openshift it gives the following warning:

Image sebp/elk runs as the root user which might not be permitted by your cluster administrator.

I Ignore this error and create deployment with this image. After that pod tries to start container but it fails with following error:

Starting periodic command scheduler cron

cron: can't open or create /var/run/crond.pid: Permission denied ...fail!

chown: changing ownership of '/var/lib/elasticsearch': Operation not permitted

I thought it i related with root user warning and then tried these steps Enable Images to Run with USER in the Dockerfile and Grant a Service Account Access to the Privileged SCC . Both of them failed with following errors:

Murats-MacBook-Pro-2:~ murat$ oc adm policy add-scc-to-group anyuid system:authenticated

Error from server (Forbidden):User "system" cannot get securitycontextconstraints.security.openshift.io at the cluster scope

Murats-MacBook-Pro-2:~ murat$ oc adm policy add-scc-to-user anyuid system:serviceaccount:elk:elk

Error from server (Forbidden): User "system" cannot get securitycontextconstraints.security.openshift.io at the cluster scope

Thanks a lot.

So i have the following Openshift/Origin architecture installed following the official Openshift/Origin documentation We also want to use the Aggregated logging setup that comes out of the box, that's why was set by using strictly the Openshift aggregated logging documentation.

So far the feedback has been excellent but i have another challenge for which i will need some help. Developers want to specify by their own the log level that will be forwarded to the Elasticsearch. Current log level is set only thru FluentD.

Is there a way to set the log level by Deployment variable and make it pass Fluentd unchanged to Elasticsearch ?

The goal is to provide people a way to set by their own the log level that will be forwarded to Elasticsearch.

The OpenShift documentation is covering how to get users and identities, but not groups. oc adm groups allows one to create a new group, add and remove users, but there doesn't seem to be a way to list all existing groups.

Is there an other way to get the groups already known to the system?

I have successfully installed Open Shift locally on my Ubuntu laptop using this guide:

https://blog.openshift.com/using-openshift-3-on-your-local-environment/

using this vagrant file: https://www.openshift.org/vm/Vagrantfile

But its a fairly old version, 1.2.0:

https://app.vagrantup.com/thesteve0/boxes/openshift-origin

Any suggestion on how to update to e.g. latest or 3.6/3.7 using the above guide?

I'm trying to activate authentification via htpasswd in my minishift 1.11.0 installation. I cannot find the master config file to set the values described in the documentation for Openshift Origin. I've searched in the minishift-VM via minishift ssh and in the minishift folders in my home folder on my Windows 7 Host.

How can I activate htpasswd for minishift 1.11.0?

EDIT: I found the master-config.yaml in the folder /var/lib/minishift/openshift.local.config/master/. I changed the content under oauthConfig as described in the Openshift documentation: https://docs.openshift.org/latest/install_config/configuring_authentication.html

The .htpasswd file is located in the same folder and referenced in the master config with it's absolute path.

But when I stop and start minishift again, the starting process ends with the following error: