summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_curator/tasks
Commit message (Collapse)AuthorAgeFilesLines
* bug 1506073. Lower cpu request for logging when it exceeds limitJeff Cantrill2017-10-271-1/+1
|
* Use "requests" for CPU resources instead of limitsPeter Portante2017-10-191-0/+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)
* Bug 1471322: logging roles based image versionsJan Wozniak2017-08-181-1/+1
| | | | | | 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-271-1/+1
| | | | creeping
* Create logging deployments with non-zero replica countsSteve Kuznetsov2017-05-221-10/+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>
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-222-0/+139
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-12 14:31:36 +0000