summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging/defaults
Commit message (Collapse)AuthorAgeFilesLines
* Adding support for ES 5.x tech preview opt inEric Wolinetz2018-02-051-0/+2
|
* Fix hosted varsMichael Gugino2017-12-051-5/+5
| | | | | | Remove hosted vars from openshift_facts. The current pattern is causing a bunch of undesired sideffects.
* Bug 1510496 - logging: honor ES PVC sizeJan Wozniak2017-11-101-1/+1
|
* Merge pull request #5748 from portante/fix-cpu-limitsScott Dodson2017-10-201-12/+22
|\ | | | | Use "requests" for CPU resources instead of limits
| * Use "requests" for CPU resources instead of limitsPeter Portante2017-10-191-12/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | bug 1489498. preserve replica and shard settingsJeff Cantrill2017-10-171-2/+0
|/
* Merge pull request #5637 from wozniakjan/1496271_fixOpenShift Merge Robot2017-10-051-2/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * Bug 1496271 - Perserve SCC for ES local persistent storageJeff Cantrill2017-10-031-2/+2
| | | | | | | | | | | | | | | | | | | | 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.
* | Reverting using uninstall variables for logging and metricsEric Wolinetz2017-09-291-1/+0
|/
* Merge pull request #5358 from wozniakjan/logging_kibana_ops/default_memoryOpenShift Merge Robot2017-09-261-2/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue logging: fix kibana and kibana-ops defaults - move kibana-ops defaults to `openshift_logging_kibana` role - set kibana-ops memory limit to 256Mi to match kibana memory limit **additional steps:** - [ ] backport to 3.6 - [ ] backport to 3.5 - [x] wait for PR #5176 to merge and rebase cc: @jcantrill
| * logging: fix kibana and kibana-ops defaultsJan Wozniak2017-09-251-2/+2
| |
* | Merge pull request #5494 from jcantrill/deprecate_escopyOpenShift Merge Robot2017-09-261-1/+0
|\ \ | |/ |/| | | | | | | | | Automatic merge from submit-queue Remove logging ES_COPY feature This PR removes the ES_COPY feature that has been deprecated since 3.3
| * Remove logging ES_COPY featureJeff Cantrill2017-09-221-1/+0
| |
* | Updating default behavior for installing metrics and logging. Separating out ↵Eric Wolinetz2017-09-221-1/+2
|/ | | | uninstall to own variable
* Creating structure to warn for use of deprecated variables and set them in a ↵Eric Wolinetz2017-09-201-29/+30
| | | | single location before they are no longer honored
* Merge pull request #5189 from wozniakjan/logging_purge_uninstallOpenShift Bot2017-08-311-0/+1
|\ | | | | Merged by openshift-bot
| * Bug 1467265 - logging: add 'purge' option with uninstallJan Wozniak2017-08-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | 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.
* | fix #5206. Default ES cpu limitJeff Cantrill2017-08-251-2/+2
|/
* use mux_client_mode instead of use_mux_clientRich Megginson2017-08-011-2/+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.
* 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.
* Fixing ops storage options being passed to openshift_logging_elasticsearch ↵ewolinetz2017-06-291-1/+1
| | | | role fixing default ops pv selector
* openshift_logging: use empty default for storage labelsFederico Simoncelli2017-06-231-1/+1
| | | | Signed-off-by: Federico Simoncelli <fsimonce@redhat.com>
* Merge pull request #4356 from nhosoi/mux_params-0OpenShift Bot2017-06-151-0/+2
|\ | | | | Merged by openshift-bot
| * Reverted most of this pr 4356 except:Noriko Hosoi2017-06-051-4/+4
| | | | | | | | | | | | | | | | | | 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.
| * Introducing fluentd/mux buffer_queue_limit, buffer_size_limit, cpu_limit, ↵Noriko Hosoi2017-06-021-2/+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
* | Merge pull request #4302 from ewolinetz/pv_node_selectorsOpenShift Bot2017-06-131-2/+2
|\ \ | |/ |/| Merged by openshift-bot
| * Allowing openshift_metrics to specify PV selectors and allow way to define ↵ewolinetz2017-05-261-2/+2
| | | | | | | | selectors when creating pv
* | add mux docs; allow to specify mux namespacesRich Megginson2017-05-311-2/+7
|/ | | | | | | | | | | 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.
* add ability to expose Elasticsearch as an external routeRich Megginson2017-05-181-0/+32
| | | | | | | | | | | | | | 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.
* bug 1441369. Kibana memory limitsJeff Cantrill2017-05-111-4/+4
| | | | | | bug 1439451. Kibana crash (cherry picked from commit 66315ebbfcfda72d6f501c441359d92ec71af7d2)
* use docker_log_driver and /etc/docker/daemon.json to determine log driverRich Megginson2017-05-091-1/+1
| | | | | | | | | | | | | | | 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.
* Correctly setting the primary and replica shard count settingsewolinetz2017-05-031-2/+0
|
* Adding way to add labels and nodeselectors to logging projectewolinetz2017-04-271-0/+4
|
* mux does not require privileged, only hostmount-anyuidRich Megginson2017-04-191-0/+11
|
* bug 1432607. Allow configuration of ES log destinationJeff Cantrill2017-03-301-0/+2
|
* Specify enterprise defaults for logging and metrics imagesScott Dodson2017-03-241-2/+0
|
* Do not use auto_expand_replicasLukáš Vlček2017-03-231-0/+4
|
* Merge pull request #3713 from ewolinetz/kibana_ops_cherrypickOpenShift Bot2017-03-231-0/+12
|\ | | | | Merged by openshift-bot
| * Cherry picking from #3711ewolinetz2017-03-201-0/+12
| |
* | Merge pull request #3647 from jcantrill/logging_specify_es_configOpenShift Bot2017-03-211-0/+2
|\ \ | |/ |/| Merged by openshift-bot
| * Allow user to specify additions to ES configJeff Cantrill2017-03-141-0/+2
| |
* | Merge pull request #3669 from ewolinetz/logging_master_api_portScott Dodson2017-03-161-1/+1
|\ \ | | | | | | Removing dependency on master facts for master_public_url default
| * | Removing dependency on master facts for master_public_url defaultewolinetz2017-03-151-1/+1
| |/
* / Cherry picked from #3657ewolinetz2017-03-151-3/+3
|/
* More logging fixesewolinetz2017-03-071-2/+2
|
* Adding some more logging defaultsewolinetz2017-03-031-8/+21
|
* Add insecure edge termination policy for kibana.Wesley Hearn2017-02-231-0/+1
|
* bug 1425321. Default the master api port based on the factsJeff Cantrill2017-02-211-1/+1
|
* Merge pull request #3381 from jcantrill/bz_1420217_default_es_memoryEric Wolinetz2017-02-161-2/+2
|\ | | | | bug 1420217. Default ES memory to be compariable to 3.4 deployer
| * bug 1420217. Default ES memory to be compariable to 3.4 deployerJeff Cantrill2017-02-161-2/+2
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 08:54:36 +0000