| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
falling back to current logic
|
|\
| |
| |
| |
| |
| |
| |
| | |
Automatic merge from submit-queue.
bug 1501599. Omit logging project from overcommit restrictions
This PR:
* Annotates the logging project to remove overcommit restrictions
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Currently, install_logging.yml in openshift_logging role
loops over other roles.
This creates a collision with the keyword 'item' in those roles.
This commit adds the loop_var as suggested by ansible warnings.
|
|\
| |
| | |
Use "requests" for CPU resources instead of limits
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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)
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Automatic merge from submit-queue.
Bug 1496271 - Perserve SCC for ES local persistent storage
ES can be modified to use node local persistent storage. This requires changing SCC and is described in docs:
https://docs.openshift.com/container-platform/3.6/install_config/aggregate_logging.html
During an upgrade, SCC defined by the user is ignored. This fix fetches SCC user defined as a fact and adds it to the ES DC which is later used.
Also includes cherrypicked fix for - Bug 1482661 - Preserve ES dc nodeSelector and supplementalGroups
cc @jcantrill
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ES can be modified to use node local persistent storage. This requires
changing SCC and is described in docs:
https://docs.openshift.com/container-platform/3.6/install_config/aggregate_logging.html
During an upgrade, SCC defined by the user is ignored. This fix fetches
SCC user defined as a fact and adds it to the ES DC which is later used.
|
| |
| |
| |
| | |
(cherry picked from commit 601e35cbf4410972c7fa0a1d3d5c6327b82353ac)
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Add logging es prometheus endpoint
This PR adds changes to add a prometheus endpoint to the logging elasticsearch pod
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Removing setting pvc size and dynamic to remove looped var setting
If we don't set openshift_logging_es_pvc_size but have `openshift_logging_es_pvc_dynamic=True` we see the variable openshift_logging_elasticsearch_pvc_size is set recursively as itself.
Addresses:
https://bugzilla.redhat.com/show_bug.cgi?id=1495150
https://bugzilla.redhat.com/show_bug.cgi?id=1496202
|
| | | |
|
| |/
|/| |
|
|/
|
|
|
|
|
|
| |
- eventrouter has its own role 'openshift_logging_eventrouter' written as
a template
- 'openshift_logging_install_eventrouter' controls whether it gets included
in the playbook or not
- deployed by default to 'default' namespace
|
|
|
|
| |
uninstall to own variable
|
| |
|
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The common uninstall would keep PVC around to prevent unwanted data loss during
reinstalls. There is a scenario where the user may want complete removal of EFK
stack including PVC.
This change adds an optional `openshift_logging_purge_logging` variable to
completely remove the EFK stack. By default, this is set to 'False' and only
works if user sets `openshift_logging_install_logging` to 'False' to initiate
the uninstallation process.
|
|\ \
| | |
| | | |
annotate the infra projects for logging to fix bz1480988
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Merged by openshift-bot
|
| | |
| | |
| | |
| | |
| | |
| | | |
Allowing to specify an image version for each logging component
https://bugzilla.redhat.com/show_bug.cgi?id=1471322
|
| |/
|/| |
|
|/ |
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
| |
| |
| | |
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
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
I should've noticed before merging...
|