summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_elasticsearch/templates/es.j2
Commit message (Collapse)AuthorAgeFilesLines
* Adding support for ES 5.x tech preview opt inEric Wolinetz2018-02-051-187/+0
|
* bug 1537857. Fix retrieving prometheus metricsJeff Cantrill2018-01-261-0/+1
|
* Relocate filter plugins to lib_utilsMichael Gugino2017-12-181-1/+1
| | | | | | | | | | | | | | This commit relocates filter_plugings to lib_utils, changes the namespacing to prevent unintended use of older versions that may be present in filter_plugins/ directory on existing installs. Add lib_utils to meta depends for roles Also consolidate some plugins into lib_utils from various other areas. Update rpm spec, obsolete plugin rpms.
* Removing config trigger for ES DC, updating to use a handler to rollout ES ↵Eric Wolinetz2017-12-141-0/+1
| | | | at the end of a deployment, allowing for override with variable
* bug 1519622. Disable rollback of ES DCsJeff Cantrill2017-12-051-0/+1
|
* dist.iteritems() no longer exists in Python 3.Jan Pazdziora2017-11-271-1/+1
|
* Bug 1452939 - change Logging & Metrics imagePullPolicyJan Wozniak2017-10-231-2/+2
| | | | | - all images logging and metrics change their default imagePullPolicy from Always to IfNotPresent
* Use "requests" for CPU resources instead of limitsPeter Portante2017-10-191-3/+4
| | | | | | | | | | | | | | | 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)
* Updating ES proxy image prefix and version to match other componentsEric Wolinetz2017-10-131-2/+2
|
* Merge pull request #5637 from wozniakjan/1496271_fixOpenShift Merge Robot2017-10-051-1/+6
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-0/+3
| | | | | | | | | | | | | | | | | | | | 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.
| * bug 1482661. Preserve ES dc nodeSelector and supplementalGroupsJeff Cantrill2017-09-291-1/+3
| | | | | | | | (cherry picked from commit 601e35cbf4410972c7fa0a1d3d5c6327b82353ac)
* | Add logging es prometheus endpointJeff Cantrill2017-10-031-1/+41
|/
* Merge pull request #5209 from wozniakjan/logging_es_probeOpenShift Bot2017-09-071-0/+13
|\ | | | | Merged by openshift-bot
| * elasticsearch: reintroduce readiness probeJan Wozniak2017-08-291-0/+13
| |
* | logging set memory request to limitJeff Cantrill2017-08-301-1/+1
| |
* | Revert "logging set memory request to limit"Scott Dodson2017-08-291-1/+1
| |
* | logging set memory request to limitJeff Cantrill2017-08-231-1/+1
|/
* Updating template parameter replica to be more unique to avoid var scope ↵ewolinetz2017-07-271-2/+2
| | | | creeping
* logging_es: temporarily disable readiness probeJan Wozniak2017-06-291-10/+0
| | | | | | | | | | The readiness probe, as currently implemented, together with the ES master discovery using the logging-es service, causes a deadlock on clusters with more than one node. Readiness probe will be reintroduced in later release. More information in: https://bugzilla.redhat.com/show_bug.cgi?id=1459430
* Merge pull request #4451 from wozniakjan/logging_es_heap_dumpScott Dodson2017-06-291-0/+3
|\ | | | | logging: write ES heap dump to persistent storage
| * logging: write ES heap dump to persistent storageJan Wozniak2017-06-141-0/+3
| |
* | bug 1457642. Use same SG index to avoid seeding timeoutJeff Cantrill2017-06-141-0/+3
|/
* Updating probe timeout and exposing variable to adjust timeout in imageewolinetz2017-06-011-2/+5
|
* Create logging deployments with non-zero replica countsSteve Kuznetsov2017-05-221-1/+1
| | | | | | | | | | | | When we currently create the set of logging `DeploymentConfig`s, we create them with zero desired replicas. This causes the deployment to immediately succeed as there is no work to be done. This inhibits our ability to use nice CLI UX features like `oc rollout status` to monitor the logging stack deployments. Instead, we should can create the configs with the correct number of replicas in the first place and stop using `oc scale` to bring them up after the fact. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
* Pulling changes from master branchewolinetz2017-05-221-3/+7
|
* Pulling in changes from masterewolinetz2017-05-221-4/+12
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-221-0/+114
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-06 12:34:03 +0000