| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
From now on, all master configurations use the api / controller split,
regardless of HA mode or previous configuration. This will be our only
supported configuration starting in 3.7 or 3.8.
|
|\
| |
| | |
Switch logging and metrics OCP image tag from 3.6.0 to v3.6
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
(cherry picked from commit 231a7c4ce27ff944d9e14169062f487f57c94dd6)
|
|
|
|
| |
openshift_logging_elasticsearch
|
|
|
|
|
|
|
|
|
|
| |
"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.
|
| |
|
|
|
|
| |
role fixing default ops pv selector
|
|
|
|
| |
Signed-off-by: Federico Simoncelli <fsimonce@redhat.com>
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
port the code that creates the external Elasticsearch routes to the
new logging roles
Have to suppress this error message:
SSL Problem illegal change cipher spec msg, conn state = 6, handshake state = 1
which is coming from the router health check, until
https://github.com/openshift/origin/issues/14515
is fixed - otherwise, the es log is spammed relentlessly
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
adding
openshift_logging_fluentd_buffer_queue_limit: 1024
openshift_logging_fluentd_buffer_size_limit: 1m
openshift_logging_mux_buffer_queue_limit: 1024
openshift_logging_mux_buffer_size_limit: 1m
and setting the matched environment variables.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \
| |_|/
|/| | |
Merged by openshift-bot
|
| | |
| | |
| | |
| | | |
selectors when creating pv
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Merged by openshift-bot
|
| | |
| | |
| | |
| | | |
ES dc creation
|
|\ \ \
| | | |
| | | | |
Merged by openshift-bot
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds the necessary documentation for the mux parameters and
behavior. This also adds new parameters which allow to specify
the namespaces mux must create by default, and which can be
optionally added.
This casts openshift_logging_use_mux to bool wherever it is used
as a boolean.
Also - use oc_service `labels` and `external_ips` which are now
available.
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| | |
This reverts commit 6b9e05d16a935d632b83eda601538bff2353e4fb, reversing
changes made to 240b923c95e04e9467c607c502c857dd86d14179.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
|
| | |
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | | |
|
|\ \ \
| | | |
| | | | |
Merged by openshift-bot
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Merged by openshift-bot
|
| |/
| |
| |
| | |
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
I should've noticed before merging...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the ability to expose Elastisearch as a route outside of the
cluster.
- `openshift_logging_es_allow_external`: True (default is False) - if this is
True, Elasticsearch will be exposed as a Route
- `openshift_logging_es_ops_hostname`: The external facing hostname to use for
the route and the TLS server certificate (default is "es." +
`openshift_master_default_subdomain`)
There are other similar parameters for the TLS server cert, key, and CA cert.
There are other similar parameters for when the OPS cluster is deployed e.g.
`openshift_logging_es_ops_allow_external`, etc.
|
|\
| |
| | |
Don't escalate privileges in local tmpdir creation
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When running `ansible-playbook` as a non-root user, if a local temporary
directory is created without explicitly not escalating privileges, the
directory will not be readable to the user running the playbook on the
controller host, which will lead to tasks like `fetch` failing to place
files into the directory.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
|
|/
|
| |
This is not the only required fix, but this does fix one of the many issues.
|
|\
| |
| |
| |
| | |
jcantrill/bz1448860_make_recovery_after_nodes_to_node_quorum
Merged by openshift-bot
|
| | |
|
|/
|
|
|
|
| |
bug 1439451. Kibana crash
(cherry picked from commit 66315ebbfcfda72d6f501c441359d92ec71af7d2)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We check the following variables, if they are defined, in the order listed
below, to see if the journald log driver is set:
* openshift_hosted_logging_use_journal
* docker_log_driver
* openshift.docker.log_driver
* openshift.docker.options (look for '--log-driver=journald')
If none of these are set, we leave openshift_logging_fluentd_use_journal
undefined, and mount both /etc/sysconfig/docker and /etc/docker
(for daemon.json) so that fluentd can determine which log driver is
being used.
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| | |
updating master config
|
| | |
|