summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_elasticsearch/tasks
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #4294 from richm/fix-es-routes-for-new-logging-rolesOpenShift Bot2017-06-161-0/+69
|\ | | | | Merged by openshift-bot
| * fix es routes for new logging rolesRich Megginson2017-06-071-0/+69
| | | | | | | | | | | | | | | | | | | | | | | | port the code that creates the external Elasticsearch routes to the new logging roles Have to suppress this error message: SSL Problem illegal change cipher spec msg, conn state = 6, handshake state = 1 which is coming from the router health check, until https://github.com/openshift/origin/issues/14515 is fixed - otherwise, the es log is spammed relentlessly
* | Use volume.beta.kubernetes.io annotation for storage-classesPer Carlson2017-06-081-1/+1
|/
* Fixing tux warnings and some final clean upewolinetz2017-05-231-5/+6
|
* Appease travisScott Dodson2017-05-221-2/+2
|
* Create logging deployments with non-zero replica countsSteve Kuznetsov2017-05-221-8/+1
| | | | | | | | | | | | When we currently create the set of logging `DeploymentConfig`s, we create them with zero desired replicas. This causes the deployment to immediately succeed as there is no work to be done. This inhibits our ability to use nice CLI UX features like `oc rollout status` to monitor the logging stack deployments. Instead, we should can create the configs with the correct number of replicas in the first place and stop using `oc scale` to bring them up after the fact. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
* Pulling changes from master branchewolinetz2017-05-221-0/+2
|
* Pulling in changes from masterewolinetz2017-05-221-18/+69
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-222-0/+250