summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_elasticsearch
Commit message (Collapse)AuthorAgeFilesLines
* Use volume.beta.kubernetes.io annotation for storage-classesPer Carlson2017-06-081-1/+1
|
* Merge pull request #4351 from ewolinetz/logging_es_readiness_probeOpenShift Bot2017-06-071-2/+5
|\ | | | | Merged by openshift-bot
| * Updating probe timeout and exposing variable to adjust timeout in imageewolinetz2017-06-011-2/+5
| |
* | specify all logging index mappings for kibanaJeff Cantrill2017-06-061-0/+1
|/
* openshift_logging: increasing *_elasticsearch_* default CPU and memoryJan Wozniak2017-05-251-4/+4
|
* 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-222-9/+2
| | | | | | | | | | | | 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-223-9/+14
|
* Adding some missing changesewolinetz2017-05-221-1/+3
|
* Pulling in changes from masterewolinetz2017-05-224-24/+97
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-2211-0/+715