Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | dist.iteritems() no longer exists in Python 3. | Jan Pazdziora | 2017-11-27 | 1 | -1/+1 |
| | |||||
* | Addressing tox errors | Eric Wolinetz | 2017-11-07 | 1 | -8/+8 |
| | |||||
* | Updating logging components image defaulting pattern to match ↵ | Eric Wolinetz | 2017-11-06 | 5 | -7/+24 |
| | | | | openshift_logging pattern | ||||
* | bug 1506073. Lower cpu request for logging when it exceeds limit | Jeff Cantrill | 2017-10-27 | 1 | -1/+1 |
| | |||||
* | Bug 1452939 - change Logging & Metrics imagePullPolicy | Jan Wozniak | 2017-10-23 | 1 | -1/+1 |
| | | | | | - all images logging and metrics change their default imagePullPolicy from Always to IfNotPresent | ||||
* | Use "requests" for CPU resources instead of limits | Peter Portante | 2017-10-19 | 3 | -3/+18 |
| | | | | | | | | | | | | | | | 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 #5289 from jcantrill/1487573_fix_allowed_es_version | OpenShift Bot | 2017-09-08 | 1 | -2/+2 |
|\ | | | | | Merged by openshift-bot | ||||
| * | bug 1487573. Bump the allowed ES versions | Jeff Cantrill | 2017-09-01 | 1 | -2/+2 |
| | | |||||
* | | logging set memory request to limit | Jeff Cantrill | 2017-08-30 | 1 | -0/+2 |
|/ | |||||
* | Revert "logging set memory request to limit" | Scott Dodson | 2017-08-29 | 1 | -2/+0 |
| | |||||
* | Merge pull request #5119 from jcantrill/logging_memory_same_as_limit | Scott Dodson | 2017-08-29 | 1 | -0/+2 |
|\ | | | | | logging set memory request to limit | ||||
| * | logging set memory request to limit | Jeff Cantrill | 2017-08-23 | 1 | -0/+2 |
| | | |||||
* | | Bug 1471322: logging roles based image versions | Jan Wozniak | 2017-08-18 | 2 | -3/+3 |
|/ | | | | | | Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322 | ||||
* | Updating template parameter replica to be more unique to avoid var scope ↵ | ewolinetz | 2017-07-27 | 2 | -2/+2 |
| | | | | creeping | ||||
* | fix curator host, port params; remove curator es volumes | Rich Megginson | 2017-05-31 | 1 | -5/+0 |
| | |||||
* | Create logging deployments with non-zero replica counts | Steve Kuznetsov | 2017-05-22 | 2 | -11/+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> | ||||
* | Decomposing openshift_logging role into subcomponent roles | ewolinetz | 2017-05-22 | 7 | -0/+311 |