summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_curator
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #5289 from jcantrill/1487573_fix_allowed_es_versionOpenShift Bot2017-09-081-2/+2
|\ | | | | Merged by openshift-bot
| * bug 1487573. Bump the allowed ES versionsJeff Cantrill2017-09-011-2/+2
| |
* | logging set memory request to limitJeff Cantrill2017-08-301-0/+2
|/
* Revert "logging set memory request to limit"Scott Dodson2017-08-291-2/+0
|
* Merge pull request #5119 from jcantrill/logging_memory_same_as_limitScott Dodson2017-08-291-0/+2
|\ | | | | logging set memory request to limit
| * logging set memory request to limitJeff Cantrill2017-08-231-0/+2
| |
* | Bug 1471322: logging roles based image versionsJan Wozniak2017-08-182-3/+3
|/ | | | | | Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322
* Updating template parameter replica to be more unique to avoid var scope ↵ewolinetz2017-07-272-2/+2
| | | | creeping
* fix curator host, port params; remove curator es volumesRich Megginson2017-05-311-5/+0
|
* Create logging deployments with non-zero replica countsSteve Kuznetsov2017-05-222-11/+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>
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-227-0/+311