summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging/README.md
Commit message (Collapse)AuthorAgeFilesLines
* allow setting of kibana env varsJeff Cantrill2018-01-261-0/+1
|
* Don't hardcode the network interface in the openshift_logging_mux roleNathan Kinder2018-01-041-0/+3
| | | | | | | | | | | The openshift_logging_mux role hardcodes the 'eth0' interface alias for determining the IP address to use for incoming external client connections. This will cause the playbook to fail with an undefined variable error on systems where an 'eth0' interface does not exist. This patch changes the default IP address for external connections to use the 'ansible_default_ipv4' fact. It also allows this to be overridden by a new 'openshift_logging_mux_external_address' variable.
* logging with static pvc: allow specifying the storage class nameBart Van Bos2017-11-061-0/+1
|
* bug 1506073. Lower cpu request for logging when it exceeds limitJeff Cantrill2017-10-271-0/+2
|
* Bug 1452939 - change Logging & Metrics imagePullPolicyJan Wozniak2017-10-231-0/+75
| | | | | - all images logging and metrics change their default imagePullPolicy from Always to IfNotPresent
* Use "requests" for CPU resources instead of limitsPeter Portante2017-10-191-9/+9
| | | | | | | | | | | | | | | 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/+3
| | | | If enabled, tho logs are stored in ES' operations index, accesible only by cluster admins.
* Quick formatting updates to the logging README.stran2017-09-281-22/+22
| | | | This is just markup formatting changes, no content was updated.
* minor update to README and removed dead filestran2017-09-271-6/+18
|
* Added new variables for logging role for remote-syslog pluginstran2017-09-271-0/+11
| | | | | | | | Includes the following code review fixes, and a rebase with upstream/master - mux.j2 template needed mux specific parameters for syslog configs - fixed bug in IF condition not checking for true-ness - updated README wording to remove ambiguity of payload_key's datatype
* Merge pull request #4973 from wozniakjan/logging_eventrouterOpenShift Merge Robot2017-09-271-2/+8
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue logging: introducing event router Initial concept integrating kubernetes events to EFK stack using [eventrouter](https://github.com/heptio/eventrouter) - **eventrouter** is deployed to logging project, has a service account and its own role to read events - **eventrouter** watches kubernetes events, marshalls them to JSON and outputs to its STDOUT - **fluentd** picks them up and inserts to elastic search logging project index Kubernetes events could be easily stored into different index. Among other ways, it could be achieved either by a fluentd filter plugin or custom eventrouter sink. Pending actions: - [x] - get our downstream and upstream images for eventrouter, don't use heptio's cc: @josefkarasek , @jcantrill , @richm
| * logging: introducing event routerJan Wozniak2017-09-261-2/+8
| | | | | | | | | | | | | | | | - 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
* | Remove logging ES_COPY featureJeff Cantrill2017-09-221-1/+0
|/
* Merge pull request #5189 from wozniakjan/logging_purge_uninstallOpenShift Bot2017-08-311-3/+2
|\ | | | | Merged by openshift-bot
| * Bug 1467265 - logging: add 'purge' option with uninstallJan Wozniak2017-08-241-3/+2
| | | | | | | | | | | | | | | | | | | | | | 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.
* | Bug 1471322: logging roles based image versionsJan Wozniak2017-08-181-0/+12
|/ | | | | | 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-4/+11
| | | | | | | | | | | | | | | | | | | | | 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/+16
| | | | (cherry picked from commit 231a7c4ce27ff944d9e14169062f487f57c94dd6)
* Bug 1466152 - Json-file log driver: Neither ↵Rich Megginson2017-07-061-1/+1
| | | | | | | | | | "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.
* Reverted most of this pr 4356 except:Noriko Hosoi2017-06-051-0/+5
| | | | | | | | | 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.
* add mux docs; allow to specify mux namespacesRich Megginson2017-05-311-0/+31
| | | | | | | | | | | 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/+27
| | | | | | | | | | | | | | 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.
* Correctly setting the primary and replica shard count settingsewolinetz2017-05-031-2/+0
|
* bug 1432607. Allow configuration of ES log destinationJeff Cantrill2017-03-301-0/+1
|
* Do not use auto_expand_replicasLukáš Vlček2017-03-231-0/+4
|
* Add insecure edge termination policy for kibana.Wesley Hearn2017-02-231-0/+1
|
* Merge pull request #3438 from jcantrill/bz_1425321_default_api_portScott Dodson2017-02-211-1/+1
|\ | | | | Bz 1425321 default api port
| * bug 1425321. Default the master api port based on the factsJeff Cantrill2017-02-211-1/+1
| |
* | bug 142026. Ensure Ops PVC prefix are initialized to empty when ops e…Jeff Cantrill2017-02-201-2/+2
|/ | | | nabled
* fix bug 1420204. Default openshift_logging_use_journal to empty so fluentd ↵Jeff Cantrill2017-02-101-2/+2
| | | | detects and is consistent with deployer
* Reverting commit 3257 and renaming master_url to openshift_logging_master_urlewolinetz2017-02-071-2/+2
|
* Merge pull request #3257 from jcantrill/bz1417261_deployer_with_35Scott Dodson2017-02-061-1/+1
|\ | | | | fixes 1417261. Points playbooks to the correct 3.5 roles for logging …
| * fixes 1417261. Points playbooks to the correct 3.5 roles for logging and metricsJeff Cantrill2017-02-021-1/+1
| |
* | openshift_logging link pull secret to serviceaccountsJeff Cantrill2017-02-031-0/+1
|/ | | | fix unlabel when undeploying
* allow openshift_logging role to specify nodeSelectorsJeff Cantrill2017-01-241-0/+3
|
* Adding to ansible spec and changing logging jks generation to be a local_actionewolinetz2017-01-201-1/+1
|
* Removing docker run strategy and make java a requirement for control hostewolinetz2017-01-201-0/+3
|
* Updating upgrade_logging to be more idempotentewolinetz2017-01-131-1/+3
|
* Creating openshift_logging role for deploying Aggregated Logging without a ↵ewolinetz2016-12-141-0/+86
deployer image