| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | logging set memory request to limit | Jeff Cantrill | 2017-08-23 | 1 | -1/+1 |
| | | |||||
| * | configure kibana index mode | Jeff Cantrill | 2017-08-10 | 4 | -0/+14 |
| | | |||||
| * | Updating PVC generation to only be done if the pvc does not already exist to ↵ | ewolinetz | 2017-08-04 | 1 | -36/+47 |
| | | | | | avoid idempotent issues | ||||
| * | Updating template parameter replica to be more unique to avoid var scope ↵ | ewolinetz | 2017-07-27 | 2 | -3/+3 |
| | | | | | creeping | ||||
| * | Updating how storage type is determined, adding bool filter in ↵ | ewolinetz | 2017-07-24 | 1 | -2/+2 |
| | | | | | openshift_logging_elasticsearch | ||||
| * | Merge pull request #4641 from wozniakjan/logging_es_probe | OpenShift Bot | 2017-07-03 | 1 | -10/+0 |
| |\ | | | | | Merged by openshift-bot | ||||
| | * | logging_es: temporarily disable readiness probe | Jan Wozniak | 2017-06-29 | 1 | -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 | ||||
| * | | Adding labels for elasticsearch and kibana services | ewolinetz | 2017-06-29 | 1 | -6/+4 |
| |/ | |||||
| * | Merge pull request #4451 from wozniakjan/logging_es_heap_dump | Scott Dodson | 2017-06-29 | 1 | -0/+3 |
| |\ | | | | | logging: write ES heap dump to persistent storage | ||||
| | * | logging: write ES heap dump to persistent storage | Jan Wozniak | 2017-06-14 | 1 | -0/+3 |
| | | | |||||
| * | | Merge pull request #4532 from kwoodson/storageclass_dynamic | Scott Dodson | 2017-06-26 | 2 | -4/+9 |
| |\ \ | | | | | | | bugzilla:1463577 - Fix for dynamic pvs when using storageclasses. | ||||
| | * | | Fixing quote issue. | Kenny Woodson | 2017-06-21 | 1 | -1/+1 |
| | | | | |||||
| | * | | Fix for dynamic pvs when using storageclasses. | Kenny Woodson | 2017-06-21 | 2 | -4/+9 |
| | | | | |||||
| * | | | Merge pull request #4364 from jcantrill/bz1457642_set_name_to_dc | OpenShift Bot | 2017-06-21 | 2 | -1/+5 |
| |\ \ \ | |/ / |/| | | Merged by openshift-bot | ||||
| | * | | bug 1457642. Use same SG index to avoid seeding timeout | Jeff Cantrill | 2017-06-14 | 2 | -1/+5 |
| | |/ | |||||
| * | | Merge pull request #4466 from portante/rufus | OpenShift Bot | 2017-06-16 | 1 | -0/+1 |
| |\ \ | | | | | | | Merged by openshift-bot | ||||
| | * | | Ensure only one ES pod per PV | Peter Portante | 2017-06-16 | 1 | -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. | ||||
| * | | Merge pull request #4294 from richm/fix-es-routes-for-new-logging-roles | OpenShift Bot | 2017-06-16 | 3 | -0/+117 |
| |\ \ | |/ |/| | Merged by openshift-bot | ||||
| | * | fix es routes for new logging roles | Rich Megginson | 2017-06-07 | 3 | -0/+117 |
| | | | | | | | | | | | | | | | | | | | | | | | | | 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 | ||||
| * | | Use volume.beta.kubernetes.io annotation for storage-classes | Per Carlson | 2017-06-08 | 1 | -1/+1 |
| |/ | |||||
| * | Merge pull request #4351 from ewolinetz/logging_es_readiness_probe | OpenShift Bot | 2017-06-07 | 1 | -2/+5 |
| |\ | | | | | Merged by openshift-bot | ||||
| | * | Updating probe timeout and exposing variable to adjust timeout in image | ewolinetz | 2017-06-01 | 1 | -2/+5 |
| | | | |||||
| * | | specify all logging index mappings for kibana | Jeff Cantrill | 2017-06-06 | 1 | -0/+1 |
| |/ | |||||
| * | openshift_logging: increasing *_elasticsearch_* default CPU and memory | Jan Wozniak | 2017-05-25 | 1 | -4/+4 |
| | | |||||
| * | Fixing tux warnings and some final clean up | ewolinetz | 2017-05-23 | 1 | -5/+6 |
| | | |||||
| * | Appease travis | Scott Dodson | 2017-05-22 | 1 | -2/+2 |
| | | |||||
| * | Create logging deployments with non-zero replica counts | Steve Kuznetsov | 2017-05-22 | 2 | -9/+2 |
| | | | | | | | | | | | | | 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 branch | ewolinetz | 2017-05-22 | 3 | -9/+14 |
| | | |||||
| * | Adding some missing changes | ewolinetz | 2017-05-22 | 1 | -1/+3 |
| | | |||||
| * | Pulling in changes from master | ewolinetz | 2017-05-22 | 4 | -24/+97 |
| | | |||||
| * | Decomposing openshift_logging role into subcomponent roles | ewolinetz | 2017-05-22 | 11 | -0/+715 |
 |
index : csa/devops/ansible-patches/openshift.git | |
| Unnamed repository; edit this file 'description' to name the repository. | Suren A. Chilingaryan |
| summaryrefslogtreecommitdiffstats |