summaryrefslogtreecommitdiffstats
path: root/playbooks/common/openshift-node/config.yml
diff options
context:
space:
mode:
authorRich Megginson <rmeggins@redhat.com>2017-07-27 09:50:03 -0600
committerRich Megginson <rmeggins@redhat.com>2017-08-01 11:12:06 -0600
commitace4a6cf7c5f9e3abea46a1811d04f4d5a03505f (patch)
tree1adeea93f394cca7d1d3e625b66c8af146993743 /playbooks/common/openshift-node/config.yml
parent1990a975c3101389631eaee925760607600a0629 (diff)
downloadopenshift-ace4a6cf7c5f9e3abea46a1811d04f4d5a03505f.tar.gz
openshift-ace4a6cf7c5f9e3abea46a1811d04f4d5a03505f.tar.bz2
openshift-ace4a6cf7c5f9e3abea46a1811d04f4d5a03505f.tar.xz
openshift-ace4a6cf7c5f9e3abea46a1811d04f4d5a03505f.zip
use mux_client_mode instead of use_mux_client
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.
Diffstat (limited to 'playbooks/common/openshift-node/config.yml')
0 files changed, 0 insertions, 0 deletions