csa/devops/ansible-patches/openshift.git/roles/openshift_logging_kibana/defaults, branch ands

allow setting of kibana env vars

2018-01-26T21:39:33+00:00

openshift_logging_kibana: fix mixing paren

2017-12-06T20:43:02+00:00

Fix hosted vars

2017-12-05T14:40:51+00:00

Remove hosted vars from openshift_facts.

The current pattern is causing a bunch of undesired sideffects.

Updating logging components image defaulting pattern to match openshift_logging pattern

2017-11-06T21:56:54+00:00

Use "requests" for CPU resources instead of limits

2017-10-19T15:02:14+00:00

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)

Merge pull request #5044 from wozniakjan/logging_role_based_image_versions

2017-08-25T23:46:36+00:00

Merged by openshift-bot

Merge pull request #4761 from wozniakjan/logging_kibana_oom

2017-08-23T14:56:21+00:00

bug 1468987: kibana_proxy OOM

Bug 1471322: logging roles based image versions

2017-08-18T07:41:14+00:00

Allowing to specify an image version for each logging component

https://bugzilla.redhat.com/show_bug.cgi?id=1471322

Updating openshift_logging_kibana default for kibana hostname

2017-07-21T20:22:32+00:00

bug 1468987: kibana_proxy OOM

2017-07-14T08:17:46+00:00

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`.