summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_eventrouter/tasks
Commit message (Collapse)AuthorAgeFilesLines
* Verify that requested services have schedulable nodes matching the selectorsVadim Rutkovsky2018-02-101-0/+7
| | | | Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
* Adding support for ES 5.x tech preview opt inEric Wolinetz2018-02-051-1/+1
|
* Remove references to deployment_typeMichael Gugino2017-12-211-2/+2
| | | | | | | Move openshift_deployment_type check into sanity_check action plugin. Remove compatibility for deployment_type. deployment_type has been deprecated for some time now.
* Include Deprecation: Convert to include_tasksRussell Teague2017-12-061-2/+2
|
* Updating logging components image defaulting pattern to match ↵Eric Wolinetz2017-11-061-0/+13
| | | | openshift_logging pattern
* Use "requests" for CPU resources instead of limitsPeter Portante2017-10-191-1/+1
| | | | | | | | | | | | | | | We now use a CPU request to ensure logging infrastructure pods are not capped by default for CPU usage. It is still important to ensure we have a minimum amount of CPU. We keep the use of the variables *_cpu_limit so that the existing behavior is maintained. Note that we don't want to cap an infra pod's CPU usage by default, since we want to be able to use the necessary resources to complete it's tasks. Bug 1501960 (https://bugzilla.redhat.com/show_bug.cgi?id=1501960)
* logging: introducing event routerJan Wozniak2017-09-263-0/+105
- eventrouter has its own role 'openshift_logging_eventrouter' written as a template - 'openshift_logging_install_eventrouter' controls whether it gets included in the playbook or not - deployed by default to 'default' namespace