Document URL: https://docs.openshift.com/enterprise/3.1/install_config/aggregate_logging.html#pre-deployment-configuration Section Number and Name: pre-deployment-configuration Describe the issue: 1. In step 2 we need information on where the certs and keys are coming from, or how the user can create these. 2. In step 4 it has you adding a service account to the the SCC that is different from the one that is created. system:serviceaccount:logging:logging-deployer vs. system:serviceaccount:logging:aggregated-logging-fluentd
Ignore #2 regarding the use of different service accounts as the service account is created during the deployer pod.
*** Bug 1288402 has been marked as a duplicate of this bug. ***
https://docs.openshift.com/enterprise/3.1/install_config/aggregate_logging.html#pre-deployment-configuration Besides
Also: In step 2 only the kibana.crt and key should be used, If other keys and json file are added to secret the kibana pod will not work when deployed. $ oc secrets new logging-deployer \ kibana.crt=/path/to/cert kibana.key=/path/to/key
It looks like major changes were made to this section since this bug was created. Some of the steps referenced are no longer there. I am going to close this bug as cantfix, but if changes still need to be made, please reopen.