Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Merge pull request #5209 from wozniakjan/logging_es_probe | OpenShift Bot | 2017-09-07 | 1 | -0/+13 |
|\ | | | | | Merged by openshift-bot | ||||
| * | elasticsearch: reintroduce readiness probe | Jan Wozniak | 2017-08-29 | 1 | -0/+13 |
| | | |||||
* | | logging set memory request to limit | Jeff Cantrill | 2017-08-30 | 1 | -1/+1 |
| | | |||||
* | | Revert "logging set memory request to limit" | Scott Dodson | 2017-08-29 | 1 | -1/+1 |
| | | |||||
* | | logging set memory request to limit | Jeff Cantrill | 2017-08-23 | 1 | -1/+1 |
|/ | |||||
* | Updating template parameter replica to be more unique to avoid var scope ↵ | ewolinetz | 2017-07-27 | 1 | -2/+2 |
| | | | | creeping | ||||
* | 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 | ||||
* | 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 |
| | | |||||
* | | bug 1457642. Use same SG index to avoid seeding timeout | Jeff Cantrill | 2017-06-14 | 1 | -0/+3 |
|/ | |||||
* | Updating probe timeout and exposing variable to adjust timeout in image | ewolinetz | 2017-06-01 | 1 | -2/+5 |
| | |||||
* | Create logging deployments with non-zero replica counts | Steve Kuznetsov | 2017-05-22 | 1 | -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 branch | ewolinetz | 2017-05-22 | 1 | -3/+7 |
| | |||||
* | Pulling in changes from master | ewolinetz | 2017-05-22 | 1 | -4/+12 |
| | |||||
* | Decomposing openshift_logging role into subcomponent roles | ewolinetz | 2017-05-22 | 1 | -0/+114 |