summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_kibana
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #4761 from wozniakjan/logging_kibana_oomScott Dodson2017-08-231-1/+1
|\ | | | | bug 1468987: kibana_proxy OOM
| * bug 1468987: kibana_proxy OOMJan Wozniak2017-07-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | We currently set the memory allocated to the kibana-proxy container to be the same as `max_old_space_size` for nodejs. But in V8, the heap consists of multiple spaces. The old space has only memory ready to be GC and measuring the used heap by kibana-proxy code, there is at least additional 32MB needed in the code space when `max_old_space_size` peaks. Setting the default memory limit to 256MB here and also changing the default calculation of `max_old_space_size` in the image repository to be only half of what the container receives to allow some heap for other `spaces`.
* | Fix syntax for when statementRodolfo Carvalho2017-08-101-3/+3
| | | | | | | | | | | | | | | | Without that, playbook runs print warnings such as this: [WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: {{ g_etcd_hosts is not defined and g_new_etcd_hosts is not defined}}
* | Updating template parameter replica to be more unique to avoid var scope ↵ewolinetz2017-07-272-2/+2
| | | | | | | | creeping
* | Updating openshift_logging_kibana default for kibana hostnameewolinetz2017-07-211-1/+1
|/
* Adding labels for elasticsearch and kibana servicesewolinetz2017-06-291-3/+2
|
* Updated to using oo_random_word for secret genewolinetz2017-06-081-2/+2
|
* Updating kibana to store session and oauth secrets for reuse, fix ↵ewolinetz2017-06-082-18/+44
| | | | oauthclient generation for ops
* Updating Kibana-proxy secret key name, fixing deleting secrets, fixed extra ↵ewolinetz2017-05-311-2/+2
| | | | ES dc creation
* Fixing tux warnings and some final clean upewolinetz2017-05-231-11/+11
|
* Appease travisScott Dodson2017-05-221-4/+4
|
* Add a readiness probe to the Kibana containerSteve Kuznetsov2017-05-221-0/+7
| | | | | | | | | In order to ensure that the Kubernetes machinery can determine when the Kibana Pods are becoming ready, we need to add a readiness probe to the Containers that make up those pods. The Kibana readiness probe simply hits the base URL at `http://localhost:5601/` and expects a 200. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
* Create logging deployments with non-zero replica countsSteve Kuznetsov2017-05-222-10/+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 branchewolinetz2017-05-222-2/+29
|
* Pulling in changes from masterewolinetz2017-05-221-2/+20
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-228-0/+464