summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_fluentd/defaults
Commit message (Collapse)AuthorAgeFilesLines
* Move more plugins to lib_utilsMichael Gugino2018-01-101-0/+1
| | | | | | | This commit continues moving plugins into lib_utils. This commit does not move any plugins for add-on roles such as logging and metrics.
* Updating logging components image defaulting pattern to match ↵Eric Wolinetz2017-11-061-2/+0
| | | | openshift_logging pattern
* Use "requests" for CPU resources instead of limitsPeter Portante2017-10-191-2/+3
| | | | | | | | | | | | | | | 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)
* Add switch to enable/disable container engine's audit log being stored in ES.Josef Karasek2017-10-111-0/+4
| | | | If enabled, tho logs are stored in ES' operations index, accesible only by cluster admins.
* Remove logging ES_COPY featureJeff Cantrill2017-09-221-2/+0
|
* Bug 1471322: logging roles based image versionsJan Wozniak2017-08-181-2/+2
| | | | | | Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322
* use mux_client_mode instead of use_mux_clientRich Megginson2017-08-011-1/+0
| | | | | | | | | | | | | | | | | | | | | Instead of the `openshift_logging_use_mux_client` boolean parameter, use `openshift_logging_mux_client_mode` which will allow us to support different mux client use cases: The value `maximal` will cause Fluentd to perform as much of the processing as possible at the local node. This currently means all of the processing *except* for the Kubernetes metadata processing, which will be done by mux. This is the currently recommended mode to use due to current scaling issues. The value `minimal` means that Fluentd will do *no* processing at all, and send the raw logs to mux for processing. This is currently not recommended to use due to current scaling issues. Ansible will warn you if you try to use this mode. `MUX_ALLOW_EXTERNAL` is no longer needed in the mux dc. mux now always operates to process external logs. The ansible setting `openshift_logging_mux_allow_external` is still required in order to set up the mux service to accept connections from outside of the cluster.
* Impl fluentd file bufferNoriko Hosoi2017-07-281-0/+2
| | | | (cherry picked from commit 231a7c4ce27ff944d9e14169062f487f57c94dd6)
* Bug 1466152 - Json-file log driver: Neither ↵Rich Megginson2017-07-061-1/+0
| | | | | | | | | | "openshift_logging_fluentd_use_journal=false" nor omitted collects the log entries https://bugzilla.redhat.com/show_bug.cgi?id=1466152 Do not set openshift_logging_fluentd_use_journal or USE_JOURNAL at all unless it is explicitly set as an ansible param. It is almost always better to let fluentd figure out which log driver docker is using.
* add back mux_client config that was removedRich Megginson2017-07-051-0/+1
| | | | | | | not sure how this got removed, during the rebase of the logging roles perhaps? Also ensure that the value used in the fluentd daemonset env var is lower cased to work with the fluentd/run.sh script.
* Pulling changes from master branchewolinetz2017-05-221-1/+1
|
* Pulling in changes from masterewolinetz2017-05-221-6/+22
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-221-0/+43