summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_elasticsearch/templates
Commit message (Collapse)AuthorAgeFilesLines
* configure kibana index modeJeff Cantrill2017-08-101-0/+2
|
* 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
| |
* | Merge pull request #4532 from kwoodson/storageclass_dynamicScott Dodson2017-06-261-0/+3
|\ \ | | | | | | bugzilla:1463577 - Fix for dynamic pvs when using storageclasses.
| * | Fix for dynamic pvs when using storageclasses.Kenny Woodson2017-06-211-0/+3
| | |
* | | Merge pull request #4364 from jcantrill/bz1457642_set_name_to_dcOpenShift Bot2017-06-212-1/+5
|\ \ \ | |/ / |/| | Merged by openshift-bot
| * | bug 1457642. Use same SG index to avoid seeding timeoutJeff Cantrill2017-06-142-1/+5
| |/
* | Merge pull request #4466 from portante/rufusOpenShift Bot2017-06-161-0/+1
|\ \ | | | | | | Merged by openshift-bot
| * | Ensure only one ES pod per PVPeter Portante2017-06-161-0/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | bug 1460564. Fixes [BZ #1460564](https://bugzilla.redhat.com/show_bug.cgi?id=1460564). Unfortunately, the defaults for Elasticsearch prior to v5 allow more than one "node" to access the same configured storage volume(s). This change forces this value to 1 to ensure we don't have an ES pod starting up accessing a volume while another ES pod is shutting down when reploying. This can lead to "1" directories being created in `/elasticsearch/persistent/${CLUSTER_NAME}/data/${CLUSTER_NAME}/nodes/`. By default ES uses a "0" directory there when only one node is accessing it.
* | fix es routes for new logging rolesRich Megginson2017-06-072-0/+48
|/ | | | | | | | | | | | 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
* Merge pull request #4351 from ewolinetz/logging_es_readiness_probeOpenShift Bot2017-06-071-2/+5
|\ | | | | Merged by openshift-bot
| * Updating probe timeout and exposing variable to adjust timeout in imageewolinetz2017-06-011-2/+5
| |
* | specify all logging index mappings for kibanaJeff Cantrill2017-06-061-0/+1
|/
* 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-222-9/+12
|
* Adding some missing changesewolinetz2017-05-221-1/+3
|
* Pulling in changes from masterewolinetz2017-05-223-6/+28
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-224-0/+293
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-18 12:21:41 +0000