Choose the project you want to hold your logging infrastructure.
Instantiate the dev-builds template to define BuildConfigs. The template has parameters to specify the repository and branch to use for the builds. The defaults are for origin master. To develop your own images, you can specify your own repos and branches as needed.
A word about the openshift-auth-proxy: it depends on the "node" base image, which is intended to be the DockerHub nodejs base image. If you have defined all the standard templates, they include a nodejs builder image that is also called "node", and this will be used instead of the intended base image, causing the build to fail. You can delete it to resolve this problem:
oc delete is/node -n openshift
The builds should start once defined; if any fail, you can retry them with:
oc start-build <component>
e.g.
oc start-build openshift-auth-proxy
This will start the builds in the background. Use oc logs -f build/ to follow the build logs, or use oc start-build --follow to run the build in the foreground and follow the build logs.
In order to deploy logging with these images, you set the
openshift-installer
inventory variable openshift_logging_image_prefix to the cluster registry location (e.g 172.30.90.128:5000/logs/).
The images can also be built locally by executing the following in the root directory of this repo:
$PREFIX=docker.io/mynamespace/myloggingprefix- $OS_TAG=v1.x make