summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_curator
Commit message (Collapse)AuthorAgeFilesLines
* Include Deprecation: Convert to include_tasksRussell Teague2017-12-061-1/+1
|
* Fix hosted varsMichael Gugino2017-12-051-0/+1
| | | | | | Remove hosted vars from openshift_facts. The current pattern is causing a bunch of undesired sideffects.
* dist.iteritems() no longer exists in Python 3.Jan Pazdziora2017-11-271-1/+1
|
* Addressing tox errorsEric Wolinetz2017-11-071-8/+8
|
* Updating logging components image defaulting pattern to match ↵Eric Wolinetz2017-11-065-7/+24
| | | | openshift_logging pattern
* bug 1506073. Lower cpu request for logging when it exceeds limitJeff Cantrill2017-10-271-1/+1
|
* Bug 1452939 - change Logging & Metrics imagePullPolicyJan Wozniak2017-10-231-1/+1
| | | | | - all images logging and metrics change their default imagePullPolicy from Always to IfNotPresent
* Use "requests" for CPU resources instead of limitsPeter Portante2017-10-193-3/+18
| | | | | | | | | | | | | | | 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)
* 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