summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_mux/templates
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #4618 from nhosoi/resource_limitsScott Dodson2017-06-291-2/+8
|\ | | | | Sync environment variables FLUENTD/MUX_CPU_LIMIT FLUENTD/MUX_MEMORY_L…
| * Sync environment variables FLUENTD/MUX_CPU_LIMIT FLUENTD/MUX_MEMORY_LIMIT ↵Noriko Hosoi2017-06-271-2/+8
| | | | | | | | with the resource limit values.
* | Bug 1465168 - mux doesn't recognize ansible boolean parameters correctlyRich Megginson2017-06-271-1/+1
|/ | | | | | https://bugzilla.redhat.com/show_bug.cgi?id=1465168 The fix is to pass the value through the `lower` filter. The value is set in defaults/main.yaml so it should always have a value.
* Merge pull request #4356 from nhosoi/mux_params-0OpenShift Bot2017-06-151-0/+8
|\ | | | | Merged by openshift-bot
| * Adding environment variables FLUENTD_CPU_LIMIT, FLUENTD_MEMORY_LIMIT, ↵Noriko Hosoi2017-06-021-0/+4
| | | | | | | | MUX_CPU_LIMIT, MUX_MEMORY_LIMIT.
| * Introducing fluentd/mux buffer_queue_limit, buffer_size_limit, cpu_limit, ↵Noriko Hosoi2017-06-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and memory_limit. Default values: openshift_logging_fluentd_cpu_limit: 100m openshift_logging_fluentd_memory_limit: 512Mi openshift_logging_fluentd_buffer_queue_limit: 1024 openshift_logging_fluentd_buffer_size_limit: 16m openshift_logging_fluentd_buffer_size_limit: 1m openshift_logging_mux_cpu_limit: 500m openshift_logging_mux_memory_limit: 1Gi openshift_logging_mux_buffer_queue_limit: 1024 openshift_logging_mux_buffer_size_limit: 1m
* | mux uses fluentd cert/key to talk to ESRich Megginson2017-05-311-1/+1
|/
* Create logging deployments with non-zero replica countsSteve Kuznetsov2017-05-221-1/+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>
* Pulling in changes from masterewolinetz2017-05-221-0/+121
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-06 05:28:51 +0000